107 lines
2.7 KiB
Markdown
107 lines
2.7 KiB
Markdown
# Relationship Between skills-vault And CCPE System
|
|
|
|
## Short Version
|
|
|
|
`skills-vault` and `ccpe-system` are complementary, not competing.
|
|
|
|
```text
|
|
skills-vault = automation Skill implementation source
|
|
ccpe-system = agentic system architecture and high-level artifacts
|
|
```
|
|
|
|
Existing CCPE content should not be migrated into `skills-vault`.
|
|
|
|
Future migrations into `skills-vault` are limited to automation Skills that live outside CCPE System.
|
|
|
|
## What Belongs In skills-vault
|
|
|
|
Use `skills-vault` for automation-oriented Skills such as:
|
|
|
|
- Markdown transformers
|
|
- file cleanup tools
|
|
- citation checkers
|
|
- report exporters
|
|
- batch processors
|
|
- source splitters
|
|
- installable Codex or Claude Code Skills
|
|
- scripts and tests that implement repeatable Skill behavior
|
|
|
|
These Skills usually have:
|
|
|
|
- a `SKILL.md`
|
|
- deterministic procedures
|
|
- scripts
|
|
- tests or fixtures
|
|
- clear file-operation boundaries
|
|
|
|
## What Belongs In CCPE System
|
|
|
|
Use `ccpe-system` for:
|
|
|
|
- CCPE-Lite prompt cards
|
|
- durable agent specs
|
|
- committees
|
|
- runtimes
|
|
- model cards
|
|
- model indexes
|
|
- cognitive model assets
|
|
- architecture registrations for important Skills
|
|
|
|
CCPE may reference a Skill from this repository, but should not duplicate the Skill source.
|
|
|
|
Business projects may also create demand for a Skill, but they should not become owners of the Skill source. If a workflow in `video-workbench`, `writing-workbench`, or another project needs a stable automation action, the reusable implementation can live in `skills-vault` and the business project can use the installed copy from `.agents/skills`.
|
|
|
|
## When To Register A Skill In CCPE
|
|
|
|
Do not register every small utility.
|
|
|
|
Create a lightweight CCPE registration only when a Skill becomes part of a larger agentic system, for example:
|
|
|
|
- a CCPE runtime calls the Skill
|
|
- a committee depends on the Skill
|
|
- an agent spec lists the Skill as a required capability
|
|
- the Skill has meaningful authority, safety, or evaluation rules
|
|
- the Skill becomes part of a repeatable workflow
|
|
|
|
## Example Registration Relationship
|
|
|
|
If `fix-title` is migrated into this repository:
|
|
|
|
```text
|
|
skills-vault/
|
|
skills/
|
|
fix-title/
|
|
SKILL.md
|
|
scripts/
|
|
tests/
|
|
```
|
|
|
|
If later needed by CCPE, CCPE may add:
|
|
|
|
```text
|
|
ccpe-system/
|
|
skills/
|
|
tool/
|
|
fix-title.skill.md
|
|
```
|
|
|
|
That CCPE file should record only architecture metadata:
|
|
|
|
```text
|
|
canonical implementation: skills-vault/skills/fix-title
|
|
installed path: C:\Users\wangq\.agents\skills\fix-title
|
|
skill type: tool-skill / transformation-skill
|
|
used by: ...
|
|
authority: ...
|
|
validation: ...
|
|
```
|
|
|
|
It should not copy implementation source from `skills-vault`.
|
|
|
|
## Current Policy
|
|
|
|
```text
|
|
Do not migrate any existing CCPE content into skills-vault.
|
|
Only migrate automation Skills outside CCPE System.
|
|
```
|