agentleFS
SaehwanParkSaehwanPark/agent-skills-archive/.agents/skills/agent-skills-archive-orchestrator/SKILL.md

agent-skills-archive-orchestrator

Skill1 starsChanged 6 months agoMITView on GitHub

Use when creating, revising, reviewing, or validating deployable skills in this repository while keeping project harness artifacts separate from the skill archive.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill for repository tasks that create, modify, review, validate, or document skills under skills/, or that change the deploy …

    line 10
  2. Very specific:

    Do not use this skill for ordinary downstream use of an installed skill.

    line 13
  3. Very specific:

    keep large optional detail in references/ or examples/

    line 33
  4. Distinctive:

    Test or validation output, including any command that could not be run.

    line 45
  5. Distinctive:

    If a task asks to install skills into this repo as a project target, call out that the target path may overlap with the repo-local harness …

    line 51

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

Agent Skills Archive Orchestrator

When to Use

Use this skill for repository tasks that create, modify, review, validate, or document skills under skills/, or that change the deploy tooling used to install those skills.

Do not use this skill for ordinary downstream use of an installed skill. Do not treat files under .agents/skills/ as archive content.

Required Inputs

  • The user request and intended target skill, if any.
  • Current contents of the affected skills/<skill-name>/ directory.
  • Any deploy-tooling files touched by the request, especially src/agent_skills_archive/deploy.py and tests/.
  • Existing repo guidance from AGENTS.md and docs/harness/agent-skills-archive/team-spec.md.

Workflow

  1. Classify the task as one or more of: new skill, skill revision, skill review, deploy-tooling change, documentation update, or harness update.
  2. Confirm the target surface:
    • deployable archive content belongs under skills/
    • repo-local agent workflow belongs under .agents/, docs/harness/, or _workspace/
  3. Inspect existing files before editing. Preserve unrelated user changes.
  4. For archive skills, keep SKILL.md discoverable:
    • include YAML frontmatter with name and description
    • match name to the skill directory
    • keep large optional detail in references/ or examples/
  5. Record intermediate handoffs in _workspace/ when the task has multiple phases or review evidence worth preserving.
  6. Validate with the narrowest useful checks:
    • uv run deploy-skills --list-skills
    • uv run deploy-skills --dry-run --skill <skill-name> for affected skills
    • uv run python -m unittest discover -s tests when deploy code or metadata behavior changed
  7. Summarize changed surfaces and validation results.

Expected Outputs

  • Updated archive skill files, deploy code, docs, or harness files as requested.
  • A short note distinguishing archive changes from project-harness changes.
  • Test or validation output, including any command that could not be run.

Validation Notes

  • The deploy command discovers only the archive source at skills/ by default.
  • Project harness skills under .agents/skills/ should have normal skill frontmatter for agent usability, but they are not part of the archive.
  • If a task asks to install skills into this repo as a project target, call out that the target path may overlap with the repo-local harness and confirm the intended destination before copying.

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.