Evidence-linked trend hypothesis
Skills become a portable capability layer
Instructions, scripts, tools, and resources are being packaged as discoverable capabilities that can move across sessions, agents, and model providers.
Current thesis
- Agent skills are emerging as a portable capability layer, but their value depends on progressive disclosure, provenance, security review, and behavioral evaluation.
- Confidence: medium.
- Supported by 4 normalized raw signals.
Source ledger
Publishable sources attached to this record.
| # | Source | Role | Public status |
|---|---|---|---|
| 1 | github.comrepo | primary receipt | source_urls |
| 2 | platform.claude.comdocs | supporting receipt | source_urls |
| 3 | github.comrepo | supporting receipt | source_urls |
| 4 | pydantic.devsource | supporting receipt | source_urls |
What is forming
A skill packages procedural knowledge with the resources needed to execute it. That can include instructions, scripts, reference files, tool access, and acceptance checks. The package can stay dormant until a task needs it, avoiding the cost and interference of loading every capability into every prompt.
Supporting evidence
- SkillsBench evaluates packages across tasks, models, and harnesses rather than judging instruction quality by inspection.
- Claude documents progressive disclosure and testing as core skill-design practices.
- Improve encodes repository audit and model-routing behavior as an inspectable skill folder.
- Pydantic AI capabilities combine instructions, tools, settings, and lifecycle hooks behind a deferred-loading interface.
Operational consequence
Treat skills like dependencies. Pin a version, preserve provenance, inspect scripts, document permissions, run task-level evals, and keep a no-skill baseline. Portability is useful only when the package remains understandable and safe outside the environment where it was authored.