agentleFS
Sign inStart free
Echo-ScionEcho-Scion/orioncortex/.agents/skills/project-operator/SKILL.md

project-operator

Skill2 starsChanged 6 days agoMITView on GitHub

Use when preparing production releases, executing deployment pre-flight checks, managing version tags, or running chaos resilience audits.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before merging a major feature branch to main or deploying to production, you MUST execute this mechanical gate sequence.

    line 17
  2. Distinctive:

    GATE 1 (Exit Code Mandate): If ANY verification script, test suite, or pre-flight check returns Exit Code > 0, the release is IMMEDIATELY …

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Operator

Your role is to manage code releases, handle technical debt, coordinate production deployment gates, and ensure deployment environments are pristine.

🧭 Sub-Intent Dispatch Matrix

  • Production Deployment Readiness (/project-operator deploy): JIT load .agents/skills/project-operator/references/prod-deploy.md
  • Release Management & Version Tagging (/project-operator release): JIT load .agents/skills/project-operator/references/release-manager.md
  • Chaos Resilience & Fault Injection (/project-operator chaos): JIT load .agents/skills/project-operator/references/chaos-engineer.md

Release Checklist & Hard Deployment Gates (MANDATORY)

Before merging a major feature branch to main or deploying to production, you MUST execute this mechanical gate sequence. Bypassing failing checks is strictly forbidden:

# 1. Check for hardcoded API keys or secrets
python .agents/scripts/orion.py scan security .

# 2. Check for dangerous SQL commands in the latest migration
python .agents/canons/global/harnesses/migration_verifier.py --file supabase/migrations/<migration_file>

# 3. Check for Context/Token bloat
python .agents/scripts/orion.py scan tokens

# 4. Execute Full Agent & System Verification
python .agents/scripts/orion.py verify_agents

Hard Gates (Non-Negotiable)

  • GATE 1 (Exit Code Mandate): If ANY verification script, test suite, or pre-flight check returns Exit Code > 0, the release is IMMEDIATELY ABORTED. Overriding or ignoring failing exit codes is FORBIDDEN.
  • GATE 2 (Clean Index Guarantee): Uncommitted git diffs, untracked temporary files, or dirty staging states block production deployment.
  • GATE 3 (Zero Secret Leakage): Any detected secret token, exposed private key, or unpinned environment variable immediately halts deployment pipelines.

📚 Mandatory Knowledge Routing (JIT References)

If your current task intersects with these domains, you MUST execute view_file on the target BEFORE writing code:

If User Prompt/Task Relates To...Immediately Load (view_file)
Chaos Engineer.agents/skills/project-operator/references/chaos-engineer.md
Release Manager.agents/skills/project-operator/references/release-manager.md
Production Deployment Readiness.agents/skills/project-operator/references/prod-deploy.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free