path-scope-example

Demonstrates paths-scoped skill loading and provides an ADR-authoring checklist for decision records.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill path-scope-example-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: path-scope-example
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/path-scope-example
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill path-scope-example-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skills that are globally relevant can clutter context when they only matter in one directory. This reference example shows how to bind a skill to a specific folder using the paths: frontmatter key, so it auto-loads only when you work inside the decisions directory and stays silent everywhere else. ## Core Features & Use Cases - Path-scoped auto-loading: The paths: frontmatter glob (_00-Project-Management/40-Decisions/**/*) makes the skill load only when files in that directory are read or written. - ADR-authoring checklist: When active, it reminds you to number ADRs sequentially, start from the 91-Templates/ADR.template.md template, record decisions in the same response, and link the ADR back to the originating story's decisions: frontmatter. - Reusable template: Copy its paths: block as the starting point for your own directory-scoped skills, with graceful degradation on hosts that ignore unknown frontmatter keys. - Use Case: While creating ADR-0077-*.md in the decisions folder, the skill auto-loads and walks you through numbering, templating, and linking without any slash command. ## Quick Start Create a new ADR file inside the _00-Project-Management/40-Decisions/ directory and let the path-scoped skill auto-load its ADR-authoring checklist.

Frequently Asked Questions about path-scope-example

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a Claude Code skill load only in a specific directory?

Add a `paths:` array to the skill's SKILL.md frontmatter containing a repo-relative glob, such as `_00-Project-Management/40-Decisions/**/*`. The skill then auto-loads only when files matching that glob are read or written.

How do I write an Architecture Decision Record in a project?

Glob existing ADR-*.md files, take the highest number and add one, then start from the ADR template. Record the decision in the same response as the work that forced it, and link the new ADR in the originating story's decisions frontmatter.

Does the paths frontmatter key work on all Claude skill hosts?

No, paths is a Claude Code loader convention, not part of the minimal skill schema. Hosts that do not recognize it ignore the key, so the skill degrades to an ordinary description-matched skill without breaking.

Is paths scoping a security boundary for skills?

No, paths is additive with description matching and only constrains where a description-match may fire. It controls auto-loading behavior by directory, not access permissions or security isolation.

When should I use path scoping instead of description matching?

Use path scoping when a skill is only relevant inside one directory, such as ADR authoring in a decisions folder. Use description matching for globally relevant skills that users explicitly invoke anywhere in the project.