メニュー
Create or update a reusable agent skill. Use when you notice a repeated pattern, when a workflow should be persisted for future sessions, or when asked to forge/create/scaffold a new skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Close implementation loops with target-bound independent evidence and a portable proof receipt. Use when an agent changes a real system and must earn a completion claim that survives the session.
First fixture skill for skdd add tests. Use when testing drop installation.
Second fixture skill for skdd add tests. Use when testing multi-skill drops.
Safely backfill historical data for a pipeline stage — scope the date range, run a dry-run, execute in chunks to avoid overwhelming the database, and verify row counts after each chunk. Use when historical data is missing, when a pipeline stage is added retroactively, or when asked to "backfill the {stage} table from {start_date}".
Add or extend data validation checks in the pipeline when data quality issues are detected — null-percentage thresholds, value ranges, referential integrity, and row-count sanity checks. Use when a pipeline breaks on bad data, when onboarding a new dataset, or when asked to "add a quality check for {column}".
Onboard a new raw dataset into the data platform — sniff the schema, generate a profiling notebook, create the ingestion job, and add an entry to the data dictionary. Use when adding a new data source, when a partner delivers a new CSV/Parquet drop, or when asked to "onboard the {name} dataset".
SOC 職業分類に基づく
| name | skillforge |
| description | Create or update a reusable agent skill. Use when you notice a repeated pattern, when a workflow should be persisted for future sessions, or when asked to forge/create/scaffold a new skill. |
| metadata | {"author":"zakelfassi","version":"2.0","spec":"agentskills.io"} |
Create well-formed, spec-compliant skills from observed patterns.
✅ Forge when:
❌ Don't forge when:
description field is the discovery surface)kebab-case, 1-64 charactersdeploy-preview, scaffold-component, triage-bugmkdir -p skills/<skill-name>
Use this skeleton:
---
name: <skill-name>
description: <what it does>. Use when <triggers>.
metadata:
forged-by: <agent-id>
forged-from: <session-or-context>
forged-reason: "<why this was created>"
---
# <Skill Name>
## Inputs
- ...
## Steps
1. ...
2. ...
## Conventions
- Project-specific patterns that apply
## Edge Cases
- Known gotchas or special handling
If the skill involves file generation or automation:
skills/<skill-name>/
├── SKILL.md
├── scripts/
│ └── run.sh # Executable automation
└── references/
└── conventions.md # Detailed reference (keeps SKILL.md lean)
Update .skills-registry.md at the project root (same level as skills/). Create it if it doesn't exist:
| <skill-name> | local | <today> | 1 | <description> |
If the project uses the machine-readable registry (.skills-registry.json), update it too — skdd forge handles both formats automatically.
When you use a skill and encounter something it doesn't cover:
last-used and increment usage-count in the registryBefore committing a new skill:
name is kebab-case, ≤64 charsdescription includes what it does AND when to use itreferences/).skills-registry.md