identifying-skill-opportunities
coreUse when deciding what raw knowledge should become a packaged skill, a reusable capability boundary, or an import edge in an agentpack skillgraph.
Agentpack - Identifying Skill Opportunities
Setup
Source knowledge:
- domains/design/knowledge/brand-guidelines.md
- domains/frontend/knowledge/component-heuristics.md
Reusable skills:
- domains/design/skills/brand-guidelines
- domains/frontend/skills/frontend-skill
Composed task skill:
- domains/design/skills/agonda-brand-frontend
imports:
- @scope/brand-guidelines
- @scope/frontend-skill
Core Patterns
Split by reusable capability
If a knowledge area should be reused compositionally in work, give it its own packaged skill.
Compose task-specific skills with import
Use a task skill when the work needs several reusable capabilities together.
Keep capability boundaries explicit
Use packaged skills and explicit import edges to expose reusable capabilities. Runtime materialization belongs downstream from the compiled graph.
Common Mistakes
HIGH Copying knowledge into one giant skill
Wrong:
One SKILL.md contains branding, frontend heuristics, research notes, and delivery instructions.
Correct:
Create packaged skills for reusable capabilities, then compose them with imports.
Flattening multiple capabilities into one skill destroys explicit dependency edges and makes maintenance coarse.
Source: maintainer interview
CRITICAL Hiding dependency boundaries inside one task skill
Wrong:
domains/brand/skills/website-ops/SKILL.md
Correct:
domains/brand/skills/copywriting/SKILL.md
domains/research/skills/interview-research/SKILL.md
domains/brand/skills/website-ops/SKILL.md # imports packaged skills
The compiled skill graph is the architectural source of truth. Reusable capability boundaries should remain explicit in packaged skills and import edges.
Source: docs/architecture.mdx
CRITICAL Omitting provenance sources for knowledge-backed skills
Wrong:
---
name: value-copywriting
description: Copy.
---
Correct:
---
name: value-copywriting
description: Copy.
---
```agentpack
source tone = "domains/value/knowledge/tone-of-voice.md"
Without `source` bindings, the skillgraph cannot explain stale state against source truth.
Source: docs/architecture.mdx
## References
- [Capability boundaries](references/capability-boundaries.md)