agentleFS
MicrosoftKnown publishermicrosoft/cobol-docs-pipeline-sample/.github/skills/functional-analysis-group-finalizer/SKILL.md

functional-analysis-group-finalizer

Skill1 starsChanged 55 days agoMITView on GitHub

Phase-K per-group AFU finalizer for ONE group declared in `config/grouping.yaml`. LLM-driven. SCAFFOLD.

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:

    Never require or create an unrequested English edition or intermediate.

    line 36
  2. Distinctive:

    Check structural parity only when multiple languages are requested.

    line 37

≈ “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

Status: scaffold. Mirror .github/skills/functional-analysis-finalizer/ at group scope.

Scope

Phase-K finalizer step only. Authoring of per-section drafts is owned by functional-analysis-group-writer.

Inputs

  • docs/_shared/_groups/<group_id>/_fa-group-bundles/_finalize.bundle.json (authoritative)
  • docs/_shared/_groups/<group_id>/_fa-group-bundles/_finalize.bundle.md (LLM-facing)
  • docs/_shared/_groups/<group_id>/_fa-group-sections/<lang>/*.md

Outputs

  • docs/<lang>/_groups/<group_id>/functional-analysis.md

Finalize exactly bundle.languages in declared order at bundle.output_paths. Never require or create an unrequested English edition or intermediate. Check structural parity only when multiple languages are requested.

Determinism rules

  • Section order in the finalized file follows the bundle's section_order[].
  • Citations to GRP-<group_id>-REQ-NNN must resolve in the matching docs/<lang>/_groups/<group_id>/requirements.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.