# skills-vault Project Overview

`skills-vault` is the source vault for automation-oriented Skills in the five-repository working system.

It owns implementation source for reusable, installable, testable automation Skills. It does not own business workflows, expert agents, CCPE runtimes, or project-specific production records.

## Position In The Five Repositories

```text
knowledge-vault   = long-term knowledge, discussions, rule discovery
writing-workbench = article projects after a writing project is already established
ccpe-system       = agents, runtimes, model cards, protocols, architecture registration
video-workbench   = video and multimodal production projects
skills-vault      = automation Skill implementation source
```

The core boundary is:

```text
Business systems raise real automation needs.
skills-vault stores reusable automation Skill source.
.agents/skills is the local runtime installation surface.
ccpe-system records architecture dependencies only when needed.
```

## Demand Sources

New Skills should come from real work, not speculative candidate lists.

There are two valid demand sources.

### Business System Support

A business system may reveal a repeated automation need while running a real workflow.

Examples of business systems:

- `video-workbench`
- `writing-workbench`
- `knowledge-vault`
- `ccpe-system`

The business system owns its project workflow, decision records, source materials, and outputs. `skills-vault` only owns a reusable automation Skill if the need becomes stable enough to implement, test, install, and reuse.

For example, `video-workbench` may need voice generation during production. The installed Skill used by that workflow lives under:

```text
C:\Users\wangq\.agents\skills
```

The source copy, if maintained here, lives under:

```text
skills-vault\skills\<skill-name>
```

`video-workbench` is a demand source, not a direct submodule or runtime consumer of the development repository.

### Local Workflow Automation

A Skill may also come from a recurring local friction point discovered during daily work.

Example:

```text
fix-title
```

This class of Skill should still satisfy the same gate: clear input, clear output, bounded side effects, and practical verification.

## What Belongs Here

Use `skills-vault` for automation Skills that are:

- repeatable
- bounded
- installable
- testable or manually verifiable
- useful across more than one session or workflow
- focused on execution rather than business judgment

Typical examples include file transformations, format repair, batch generation, export helpers, validation helpers, and local CLI wrappers.

## What Does Not Belong Here

Do not put these in `skills-vault`:

- deep writing workflows
- article premise or outline judgment
- expert reviewer personas
- CCPE agents, committees, or runtimes
- model cards or model indexes
- speculative Skill candidates without a real workflow source
- project-specific production artifacts

## Registry Policy

`registry/skills-index.md` tracks real Skills already managed by this repository.

Do not use the registry as a speculative backlog. A Skill should be registered only after a real demand has produced concrete Skill source maintained by this repository.

## Installation Boundary

This repository is not the runtime install surface.

```text
Source of truth:      C:\Users\wangq\Documents\Codex\skills-vault\skills
Installed runtime:    C:\Users\wangq\.agents\skills
Architecture records: C:\Users\wangq\Documents\Codex\ccpe-system
```

Business systems should normally use installed Skills from `.agents/skills`, not import directly from this development repository.

## Working Rule

When a new automation need appears, first ask:

```text
Is this a real repeated action from a workflow, or just a possible future idea?
```

Only real repeated actions should become Skill work in this repository.