agentleFS
Procesio-ExternalsProcesio-Externals/procesio-cli/skills/procesio-cli-maintainer/SKILL.md

procesio-cli-maintainer

Skill5 starsChanged 3 months agoApache-2.0View on GitHub

Change or review the procesio-cli repository source code. Use to add a new CLI action, edit a CLI manifest or implementation, change a registry or MCP server, modify an agent runtime, generated capability router, CLAUDE.md synchronization, CI gate, tests, credential handling, JSON contract, or reversibility policy; use for repository implementation, diffs, broken integration references, and manifest-to-skill synchronization. Do not use for PROCESIO workspace operations or when the primary deliverable is an Agent Skill package, SKILL.md authoring, skill routing boundaries, or skill behavioral evaluation.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Treat tools, agents, skills, generated documentation, and tests as one versioned contract.

    line 29
  2. Very specific:

    Read references/change-contract.md before changing a capability, references/mcp-compatibility.md before changing MCP, and …

    line 46
  3. Very specific:

    Reproduce or record the baseline: Add a failing test or evaluation before changing behavior.

    line 50
  4. Distinctive:

    Implement one verifiable unit: Avoid unrelated cleanup and broad renames.

    line 53
  5. Distinctive:

    Regenerate structural outputs: Never hand-edit generated action manuals or router blocks as the sole source of change.

    line 54
  6. Distinctive:

    Review security and compatibility: Check secret handling, path confinement, irreversible-action classification, retry behavior, and old …

    line 57
  7. Very specific:

    Run generators appropriate to the changed manifest before --check.

    line 76
  8. Distinctive:

    No new action without manifest arguments, stable output/error behavior, tests, discoverability, and reversibility classification.

    line 80
  9. Very specific:

    No skill integration without the fixed-rubric and baseline evidence required by agent-skill-engineer.

    line 81
  10. Distinctive:

    No reference-heavy skill unless the client can read its path-confined relative files safely.

    line 82
  11. Distinctive:

    No mutation workflow that ends without direct state verification.

    line 83

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Maintain procesio-cli

Treat tools, agents, skills, generated documentation, and tests as one versioned contract. Make the smallest independently verifiable change that preserves existing clients.

Boundary

  • Using the repository to operate a workspace belongs to procesio-cli.
  • Product advice belongs to procesio-platform-advisor.
  • Optimizing a user's SQL belongs to sql-server-optimizer.
  • Creating, refactoring, auditing, or behaviorally evaluating an Agent Skill as the primary artifact belongs to agent-skill-engineer. Return here for repository-specific integration, generation, CI, translations, or release controls.

Sources of truth

  • A tool or agent manifest defines its executable public surface.
  • The registry discovers manifests; avoid hardcoded capability inventories.
  • Generated router/manual files must be reproducible from structural sources.
  • A skill's frontmatter defines discovery; its body defines the decision workflow; references hold detail; scripts enforce deterministic work.
  • Runtime behavior and stable JSON output are stronger evidence than prose.

Read references/change-contract.md before changing a capability, references/mcp-compatibility.md before changing MCP, and references/skill-authoring.md when integrating an already-designed skill into this repository. Load agent-skill-engineer for the skill-specific design and evaluation method.

Change workflow

  1. Reproduce or record the baseline. Add a failing test or evaluation before changing behavior. For code, exercise the real contract boundary. For a skill integration, preserve the immutable skill baseline and evidence supplied by agent-skill-engineer.
  2. Trace ownership. Identify manifest, dispatcher, implementation, generated outputs, callers, safety classification, tests, translations, and documentation affected by the change.
  3. Design the public shape first. Set action name, typed arguments, output/error shape, mutability, idempotency, and verification path before implementation.
  4. Implement one verifiable unit. Avoid unrelated cleanup and broad renames.
  5. Regenerate structural outputs. Never hand-edit generated action manuals or router blocks as the sole source of change.
  6. Run focused tests, then the full suite. Include platform-neutral tests; credentials and live infrastructure must not be required for unit tests.
  7. Verify the actual surface. Invoke the command or MCP operation through the same path a client uses and inspect its JSON, stderr, exit code, and side effects.
  8. Review security and compatibility. Check secret handling, path confinement, irreversible-action classification, retry behavior, and old client calls.
  9. Commit only a green unit. State evidence and any live check that remains unavailable.

Repository gates

Run these offline gates from the configured source checkout with its dependencies already installed; installed skill directories are not repository roots. Coding agents read package references natively relative to the skill root. CLI/MCP resource retrieval and bounded query extensions are optional installed capabilities, not prerequisites for loading skills.

The portfolio migration requires maintainer merge approval; publication is not approval or proof of behavioral improvement. It includes offline structural/catalog/routing/governance checks, not behavioral runners, live field examples or historical receipt documents. Historical catalog fixtures are not a current-package pass: the new extraction gate remains blocked pending fresh qualification evidence.

python -m pytest tools agents dashboard webplatform skills -q
python scripts/validate-skills.py --strict-warnings
python scripts/evaluate-skills.py --catalog skills/evals/baseline-catalog.json --verify-baseline skills/evals/baseline.json
python scripts/evaluate-skill-routing.py --min-accuracy 0.95 --max-collision-rate 0
python scripts/check-skill-governance.py
python scripts/secret_scan.py
python scripts/build-router.py --check

Run generators appropriate to the changed manifest before --check.

Completion verification

  • No new action without manifest arguments, stable output/error behavior, tests, discoverability, and reversibility classification.
  • No skill integration without the fixed-rubric and baseline evidence required by agent-skill-engineer.
  • No reference-heavy skill unless the client can read its path-confined relative files safely; native file reads suffice. CLI/MCP resource retrieval is optional and must be verified against the installed schema.
  • No mutation workflow that ends without direct state verification.
  • No “CI is green” claim unless the actual workflow run or full local command set was observed.

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.