# Path Scope Example

> path-scope-example (reference: directory-scoped skill)

- Skill: `data-ai-xyz/path-scope-example` (Agent Skill)
- Install (CLI): `npx skillmds@latest add data-ai-xyz/path-scope-example`
- Raw SKILL.md: https://api.skillmd.com/api/skills/data-ai-xyz/path-scope-example/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: DATA-AI-XYZ (https://skillmd.com/u/data-ai-xyz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/data-ai-xyz/path-scope-example

---


# path-scope-example (reference: directory-scoped skill)

This skill is the kit's **worked example of `paths:` scoping** (ADR-0010, proven by STORY-17.2.01). Unlike every other Tandem skill — which is globally relevant and explicitly slash-invoked — this one is bound by its `paths:` frontmatter to **`_00-Project-Management/40-Decisions/`**, so Claude auto-loads it only while reading/writing files in that directory. Outside the decisions folder it stays silent.

It is intentionally minimal and doubles as a genuine, directory-local helper: a quick ADR-authoring checklist.

## When this activates

Auto-loads when you touch a file under `_00-Project-Management/40-Decisions/` (e.g. creating `ADR-0077-*.md`). It does **not** auto-load when you're working in `32-Stories/`, `skills/`, or anywhere else — that's the whole point of path-scoping.

## ADR-authoring reminder (the local concern)

1. **Number sequentially across the whole project.** Glob `ADR-*.md` in this folder, take the max `NNNN`, add 1. No folder grouping.
2. **Start from the template** — `91-Templates/ADR.template.md`. Don't redraft headings from memory.
3. **Record the decision in the same response** as the work that forced it (ADR-on-the-spot).
4. **Link back** — add the new `ADR-NNNN` to the originating story's `decisions:` frontmatter array.
5. **Commit, don't hedge** — an ADR commits to one option; list the rejected ones under `## Alternatives considered`.

## How to reuse this pattern

To make one of your own skills directory-scoped, copy the `paths:` block above and point it at your directory's glob (repo-relative, `**` recursion, brace expansion — same format as `.claude/rules/` path-specific rules). Remember `paths:` is **additive** with `description:` — it constrains *where* a description-match may fire; it is not a security control. See `90-Standards/CLAUDE-CODE-CONFIG.md` §2.3.1 for when to path-scope vs description-match.

**Portability note:** `paths:` is a Claude Code loader convention, not part of the minimal skill-frontmatter schema (`name` + `description`). Hosts and validators that don't recognise it ignore unknown frontmatter keys, so on such hosts (e.g. Claude Cowork surfaces that only description-match) this skill degrades gracefully to an ordinary description-matched skill — nothing breaks, it just loses the auto-load-on-directory behaviour.