One change
PDF Processing
agents-and-tools/agent-skills/best-practices
Nearest release: v2.1.233, published under an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
agents-and-tools/agent-skills/best-practices Changed · +34 / -28 lines
from line 270
The complete Skill directory structure might look like this: -```text -pdf/ -├── SKILL.md # Main instructions (loaded when triggered) -├── FORMS.md # Form-filling guide (loaded as needed) -├── reference.md # API reference (loaded as needed) -├── examples.md # Usage examples (loaded as needed) -└── scripts/ - ├── analyze_form.py # Utility script (executed, not loaded) - ├── fill_form.py # Form filling script - └── validate.py # Validation script -``` +* `pdf/` + * `SKILL.md`: Main instructions (loaded when triggered) + + * `FORMS.md`: Form-filling guide (loaded as needed) + + * `reference.md`: API reference (loaded as needed) + + * `examples.md`: Usage examples (loaded as needed) + + * `scripts/` + + * `analyze_form.py`: Utility script (executed, not loaded) + * `fill_form.py`: Form filling script + * `validate.py`: Validation script + #### Pattern 1: High-level guide with references ````markdown
from line 318
For Skills with multiple domains, organize content by domain to avoid loading irrelevant context. When a user asks about sales metrics, Claude only needs to read sales-related schemas, not finance or marketing data. This keeps token usage low and context focused. -```text -bigquery-skill/ -├── SKILL.md (overview and navigation) -└── reference/ - ├── finance.md (revenue, billing metrics) - ├── sales.md (opportunities, pipeline) - ├── product.md (API usage, features) - └── marketing.md (campaigns, attribution) -``` +* `bigquery-skill/` + * `SKILL.md` (overview and navigation) + + * `reference/` + + * `finance.md` (revenue, billing metrics) + * `sales.md` (opportunities, pipeline) + * `product.md` (API usage, features) + * `marketing.md` (campaigns, attribution) + ````markdown SKILL.md # BigQuery Data Analysis
from line 1066
**Example:** -```text -bigquery-skill/ -├── SKILL.md (overview, points to reference files) -└── reference/ - ├── finance.md (revenue metrics) - ├── sales.md (pipeline data) - └── product.md (usage analytics) -``` +* `bigquery-skill/` + + * `SKILL.md` (overview, points to reference files) + + * `reference/` + + * `finance.md` (revenue metrics) + * `sales.md` (pipeline data) + * `product.md` (usage analytics) When the user asks about revenue, Claude reads SKILL.md, sees the reference to `reference/finance.md`, and calls bash to read just that file. The sales.md and product.md files remain on the filesystem, consuming zero context tokens until needed. This filesystem-based model is what enables progressive disclosure. Claude can navigate and selectively load exactly what each task requires.