orcaflex-yaml-gotchas-execution-validating-generated-yaml

Sub-skill of orcaflex-yaml-gotchas: Execution: Validating Generated YAML.

5 stars

Best use case

orcaflex-yaml-gotchas-execution-validating-generated-yaml is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of orcaflex-yaml-gotchas: Execution: Validating Generated YAML.

Teams using orcaflex-yaml-gotchas-execution-validating-generated-yaml should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/execution-validating-generated-yaml/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/marine-offshore/orcaflex-yaml-gotchas/execution-validating-generated-yaml/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/execution-validating-generated-yaml/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How orcaflex-yaml-gotchas-execution-validating-generated-yaml Compares

Feature / Agentorcaflex-yaml-gotchas-execution-validating-generated-yamlStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of orcaflex-yaml-gotchas: Execution: Validating Generated YAML.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Execution: Validating Generated YAML

## Execution: Validating Generated YAML


```python
import OrcFxAPI

def validate_yaml_round_trip(yaml_path):
    """Load YAML into OrcFxAPI and check for errors."""
    model = OrcFxAPI.Model()
    try:
        model.LoadData(yaml_path)
        return {"valid": True, "errors": []}
    except OrcFxAPI.OrcaFlexError as e:
        error_msg = str(e)
        errors = [error_msg]

        # Diagnose common YAML gotchas
        if "Change not allowed" in error_msg:
            errors.append("Likely dormant property issue — check mode-setting property order")
        if "not a valid" in error_msg and "name" in error_msg.lower():
            errors.append("Reference to undefined object — check section ordering")
        if "alias" in error_msg.lower():
            errors.append("YAML aliases not supported — use NoAliasDumper")

        return {"valid": False, "errors": errors}
```

Related Skills

OrcaFlex Specialist Skill

5
from vamseeachanta/workspace-hub

```yaml

orcaflex-reporting-fixture-proof-pattern

5
from vamseeachanta/workspace-hub

Build and extend fixture-backed OrcaFlex reporting proof paths in digitalmodel using stable metadata baselines, normalized HTML snapshots, and reusable reporting test helpers.

digitalmodel-worktree-test-execution-with-shared-venv

5
from vamseeachanta/workspace-hub

Run digitalmodel tests from isolated worktrees without uv editable-dependency failures by using the main repo's existing virtualenv and PYTHONPATH.

digitalmodel-orcawave-orcaflex-proof-workflows

5
from vamseeachanta/workspace-hub

Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.

plan-gated-issue-execution-wave

5
from vamseeachanta/workspace-hub

Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.

orcawave-orcaflex-readiness-audit

5
from vamseeachanta/workspace-hub

Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.

work-around-merge-conflicts-in-test-execution

5
from vamseeachanta/workspace-hub

Run tests when repo has unresolved merge conflicts in config files by bypassing broken configs and executing tests directly

wave-based-parallel-plan-execution

5
from vamseeachanta/workspace-hub

Orchestrate phase execution by discovering dependencies, grouping into waves, spawning subagents, and collecting results with optional wave filtering

digitalmodel-orcawave-orcaflex-workflow

5
from vamseeachanta/workspace-hub

Current-state workflow for navigating and extending digitalmodel OrcaWave/OrcaFlex capabilities across code, tests, issues, queue tooling, and licensed-machine boundaries.

plan-governance-vs-execution-boundary-for-adversarial-review

5
from vamseeachanta/workspace-hub

Keep stale-approval/governance remediation out of execution-path pseudocode, TDD, files-to-change, and deliverable acceptance when hardening a GitHub issue plan under adversarial review.

orcawave-orcaflex-semantic-proof-wave-closeout

5
from vamseeachanta/workspace-hub

Close out an OrcaWave/OrcaFlex semantic-proof wave after a PR merges, split unrelated CI blockers, and seed the next semantic-proof issue wave without duplicating existing issues.

interactive-issue-execution-worktree-guardrails

5
from vamseeachanta/workspace-hub

Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.