Skip to content
Back to skills

Best Practices

ASecurity

Sub-skill of oil-and-gas: Best Practices.

  • 17 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 9, 2026
documentationgoapi

Works with

  • api

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill best-practices --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Best Practices?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Best Practices
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-best-practices-e3b16d22/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-best-practices-e3b16d22)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: oil-and-gas-best-practices
description: 'Sub-skill of oil-and-gas: Best Practices.'
version: 1.0.0
category: engineering
type: reference
scripts_exempt: true
---

# Best Practices

## Best Practices


### Data Quality

1. Always validate input data ranges against physical constraints
2. Check for missing or anomalous values before analysis
3. Apply appropriate data cleaning techniques
4. Document data sources and assumptions

### Analysis Workflow

1. Start with exploratory data analysis
2. Apply domain-specific correlations (Standing, Beggs-Brill, etc.)
3. Validate results against field analogues
4. Perform sensitivity analysis
5. Document uncertainties explicitly

### Safety and Environment

1. Follow HSE guidelines in all technical work
2. Consider environmental impact in design decisions
3. Apply risk assessment methodologies (bow-tie, HAZID/HAZOP)
4. Maintain regulatory compliance throughout

### Code Standards

1. Use industry-standard units (field or SI — be explicit)
2. Include unit conversion utilities
3. Implement robust error handling with physical constraint checks
4. Provide comprehensive docstrings
5. Follow PEP 8 style guide

### Response Standards When Providing Technical Solutions

1. Start with fundamentals: explain underlying principles before complex solutions
2. Use industry terminology with explanations where needed
3. Include calculations: show relevant equations and example calculations
4. Reference standards: cite applicable API, ISO, or regulatory standards
5. Consider safety: always prioritize HSE considerations in recommendations

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.