agents-arwaky / tools
AGENTS.md0 starsChanged 3 days agoMITView on GitHub
AGENTS.md operational guide for skill-design pack.
In this repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aes-docsSkill
- aes-fixSkill
- aes-layerSkill
- aes-migrationSkill
- android-emulator-linux-gpsSkill
- computer-useSkill
- flatpak-chromium-automationSkill
- qwen-webSkill
- grok-buildSkill
- hermes-agentSkill
- omnirouteSkill
- orcaSkill
- account-managerSkill
- brave-setupSkill
- password-managerSkill
- codegraphSkill
- deep-cleanSkill
- dogfoodSkill
- reviewSkill
- systematic-debuggingSkill
- blender-arwakySkill
- comfyuiSkill
- llm-writingSkill
- vision-arwakySkill
- playwright-toolingSkill
- setup-ci-quality-gatesSkill
- statuslineSkill
- systemd-headless-serviceSkill
- xdg-spec-complianceSkill
- figcraft-builderSkill
- figcraft-iconsSkill
- figcraft-motionSkill
- figcraft-prototyperSkill
- figcraft-reviewSkill
- figcraftSkill
- figcraft-svgSkill
- figcraft-typographySkill
- github-authSkill
- issue-makerSkill
- issue-workerSkill
- mergifySkill
- pr-babysitSkill
- releasingSkill
- repo-managerSkill
- ascii-artSkill
- ascii-videoSkill
- gif-searchSkill
- media-acquisitionSkill
- docxSkill
- emailSkill
- google-workspaceSkill
- notionSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- competitor-news-monitorSkill
- product-price-monitorSkill
- weekly-review-planningSkill
- arxivSkill
- The first 60 shown.
The file
Files
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
| Aspect | Detail |
| Language | Python |
| Environment | uv (Python package manager) |
| Artifacts | SKILL.md, references/, scripts/ |
| Package Manager | uv |
| Version Probe | uv --version |
| Setup | uv sync |
| Activation | source .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 testsCommands
| Category | Command | Scope | CI Gate |
| Test (all) | uv run pytest skills/skill-authoring/skill-design/modules/skills_design/tests -q | All | ci.yml: Module tests |
| Test (unit) | uv run pytest skills/skill-authoring/skill-design/modules/skills_design/tests -q -m "not dogfood" | One unit | ci.yml: Skills and shared tests |
| Test (file) | uv run pytest <path-to-test-file> -q | One file | ci.yml: Module tests |
| Lint | sac lint | All | ci.yml: Skill pack lint |
| Type Check | uv run mypy skills/skill-authoring/skill-design/modules/skills_design | All | ci.yml: Python compile check |
| Arch Scan | lint-arwaky scan skills/skill-authoring/skill-design | All | ci.yml: Architecture scan |
Reference
| Artifact | Purpose | Link |
| README | What the tool does, every command, install | README.md |
| CONTRIBUTING | Branch, commit, and PR conventions | CONTRIBUTING.md |
| PRD | What the product does and why | PRD.md |
| ROADMAP | What ships next, in order | ROADMAP.md |
| ARCHITECTURE | Layer contract for every crate | ARCHITECTURE.md |
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
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.

