Intent Layer
Set up hierarchical Intent Layer (AGENTS.md files) for codebases. Use when initializing a new project, adding context infrastructure to an existing repo, user asks to set up AGENTS.md, add intent layer, make agents understand the codebase, or scaffolding AI-friendly project documentation.
Install
/plugin marketplace add crafter-station/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add crafter-station/skills --skill intent-layergit clone --depth 1 https://github.com/crafter-station/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/intent-layer ~/.claude/skills/intent-layerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Intent Layer Hierarchical AGENTS.md infrastructure so agents navigate codebases like senior engineers. ## Core Principle **Only ONE root context file.** CLAUDE.md and AGENTS.md should NOT coexist at project root. Child AGENTS.md in subdirectories are encouraged for complex subsystems. ## Workflow ``` 1. Detect state scripts/detect_state.sh /path/to/project → Returns: none | partial | complete 2. Route none/partial → Initial setup (steps 3-5) complete → Maintenance (step 6) 3. Measure [gate - show table first] scripts/analyze_structure.sh /path/to/project scripts/estimate_tokens.sh /path/to/each/source/dir 4. Decide No root file → Ask: CLAUDE.md or AGENTS.md? Has root file → Add Intent Layer section + child nodes if needed 5. Execute Use references/templates.md for structure Use references/node-examples.md for real-world patterns Validate: one root, READ-FIRST directive, <4k tokens per node 6. Maintenance mode (when state=complete) Ask user: a) Audit nodes → Use references/capture-protocol.md for SME questions b) Find candidates → Re-measure tokens, suggest new nodes c) Both ``` ## When to Create Child Nodes | Signal | Action | |--------|--------| | >20k tokens in directory | Create AGENTS.md | | Responsibility shift | Create AGENTS.md | | Hidden contracts/invariants | Document in nearest ancestor | | Cross-cutting concern | Place at LCA |
Details
- Skill name
intent-layer- Repository
- crafter-station/skills
- Path
skills/intent-layer/SKILL.md- License
- MIT
- Repo updated
- 7 September 2026
FAQ
What does the Intent Layer skill do?
Set up hierarchical Intent Layer (AGENTS.md files) for codebases. Use when initializing a new project, adding context infrastructure to an existing repo, user asks to set up AGENTS.md, add intent layer, make agents understand the codebase, or scaffolding AI-friendly project documentation.
How do I install the Intent Layer skill?
Claude Code plugin: /plugin marketplace add crafter-station/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Intent Layer popular?
It lives in crafter-station/skills, which has 115 GitHub stars and 15 forks.
Related skills
Obsidian Plugin Release
115crafter-station/skills
Release a new version of an Obsidian community plugin without forgetting steps. Use when: (1) user says "release the plugin", "bump <plugin> to X.Y.Z", "ship a new Obsidian release", "tag a new plugin version", "publish to the obsidian directory", (2) the working directory contains manifest.json + main.js + versions.json (Obsidian plugin signature), (3) user wants to scaffold the release workflow into an existing plugin (`scaffold-workflow` arg). Handles version bump across manifest.json + package.json + versions.json, build, lint, conventional commit, signed annotated tag, push, and lets the
CLI Audit
115crafter-station/skills
Audit an existing CLI against cli-build: how well an agent can operate it and how well a human can read it. Use when the user wants to audit a CLI, check whether a tool is agent-first, find out what a published CLI got wrong, grade a CLI's human output, verify that named safety features are actually wired, or prepare a patch list before improving an existing command-line tool. Reports findings with evidence; it does not patch.
CLI Build
115crafter-station/skills
Design and build a CLI that an AI agent can operate safely and a human can supervise. Use when the user wants to build a CLI, wrap an API in a command-line tool, build a CRUD or local-first tool over a database or filesystem the user already owns, add --json or --dry-run to an existing CLI, design a trust ladder or approval gate for risky commands, wrap an async API so agents do not write their own poll loop, or decide how to distribute a CLI (npm, native binary, source). Runs on its own when the contract is yours to define; follows a surface-recon report when the target is someone else's serv
Skill Gen
115crafter-station/skills
Deprecated. Auto-generate Claude skills from documentation URLs using Firecrawl agent. Use when user wants to create a skill from docs, API references, or tool homepages. Asks up to 3 clarifying questions before deep extraction. Supports topic focus (e.g., "only auth endpoints") and outputs to local .claude/skills/ by default. No longer recommended: the generated output needed enough rewriting that authoring the SKILL.md by hand was faster.
Dws
121stvlynn/dingtalk-wukong-skills
管理钉钉产品能力(AI表格/日历/通讯录/文档/机器人/待办/邮箱/听记/AI应用/审批/日志/钉盘等)。当用户需要操作表格数据、管理日程会议、查询通讯录、发送消息通知、处理审批流程、查看听记摘要、创建应用/系统/管理后台/业务工具、查看日报周报、管理钉盘文件时使用。
Algo Forecast Arima
248asgard-ai-platform/skills
Build ARIMA models for time series forecasting with trend and seasonality decomposition. Use this skill when the user needs to forecast future values from historical sequential data, test for stationarity, or select ARIMA parameters — even if they say 'time series forecast', 'predict next month sales', or 'ARIMA model'.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.