agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/skill-authoring/tools/AGENTS.md

agents-arwaky / tools

AGENTS.md0 starsChanged 3 days agoMITView on GitHub

AGENTS.md operational guide for skill-design pack.

The file

Files
AGENTS.md

AGENTS — skill-design

Agent Overview

skill-design is the skill-authoring skill that keeps the skill tree clean, correct, and consolidated. It runs one of three modes per invocation: --create builds a publishable SKILL.md plus its references/ from a described job, --improve audits an existing skill against the shared lint standard and applies the repair edit recipe, and --prune collapses duplicate or same-purpose skills into one folder and archives the dropped duplicates. Agents generating code, docs, or suggestions must only edit files under skills/skill-authoring/skill-design/ and must keep every flag and mode term in lockstep across SKILL.md and its reference files.

Runtime

AspectDetail
LanguagePython
Environmentuv (Python package manager)
ArtifactsSKILL.md, references/, scripts/
Package Manageruv
Version Probeuv --version
Setupuv sync
Activationsource .venv/bin/activate

Project Structure

.
├── PRD.md                      # What the skill does and why
├── ROADMAP.md                  # What ships next, in order
├── README.md                   # How to use/run
├── AGENTS.md                   # This file — how to work here safely
├── CONTRIBUTING.md             # Branch, commit, and PR conventions
├── ARCHITECTURE.md             # Layer contract and linter rule catalog
├── SKILL.md                    # Skill frontmatter + routing table
├── lint_arwaky.config.yaml     # Lint gate configuration
├── template/                   # Canonical SKILL.md and reference templates
├── scripts/                    # Non-trivial logic referenced by SKILL.md
└── modules/skills_design/      # AES layer implementation
    ├── src/                    # agent + capability layers
    ├── shared/src/skills_design/  # shared kernel (contract, taxonomy, utility)
    └── tests/                  # unit / integration / e2e / smoke tests

Commands

CategoryCommandScopeCI Gate
Test (all)uv run pytest skills/skill-authoring/skill-design/modules/skills_design/tests -qAllci.yml: Module tests
Test (unit)uv run pytest skills/skill-authoring/skill-design/modules/skills_design/tests -q -m "not dogfood"One unitci.yml: Skills and shared tests
Test (file)uv run pytest <path-to-test-file> -qOne fileci.yml: Module tests
Lintsac lintAllci.yml: Skill pack lint
Type Checkuv run mypy skills/skill-authoring/skill-design/modules/skills_designAllci.yml: Python compile check
Arch Scanlint-arwaky scan skills/skill-authoring/skill-designAllci.yml: Architecture scan

Reference

ArtifactPurposeLink
READMEWhat the tool does, every command, installREADME.md
CONTRIBUTINGBranch, commit, and PR conventionsCONTRIBUTING.md
PRDWhat the product does and whyPRD.md
ROADMAPWhat ships next, in orderROADMAP.md
ARCHITECTURELayer contract for every crateARCHITECTURE.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.