agentleFS
creanlabcreanlab/agent-genome-lab/.agents/skills/skill-package-builder/SKILL.md

skill-package-builder

Skill2 starsChanged 4 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Check for overlapping or conflicting scopes.

    line 19
  2. Distinctive:

    Write a small package JSON with activation policy and included skills.

    line 20
  3. Distinctive:

    Keep the published runtime skill short and operational.

    line 26

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

Skill Package Builder

Purpose

Compose admitted skills into compact, task-oriented packages that can be published to .agents/skills/.

Use when

  • several admitted skills routinely co-activate,
  • a maintainer needs a runtime-ready package,
  • or metadata-first retrieval should resolve to a small operational surface.

Inputs

  • admitted skill IDs,
  • target package goal,
  • guardrails for the task domain,
  • optional publish target under .agents/skills/.

Procedure

  1. Select only admitted skills.
  2. Check for overlapping or conflicting scopes.
  3. Write a small package JSON with activation policy and included skills.
  4. Publish a concise SKILL.md only if the package is stable enough for runtime use.
  5. Record belong_to_package relations in the relation graph.

Guardrails

  • Packages are for composition, not for hiding unresolved candidate skills.
  • Keep the published runtime skill short and operational.
  • Preserve metadata-first loading: package first, full skills only on match.

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.