القائمة
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 ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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".
| 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","plugin":"skdd-claude"} |
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 .claude/skills/<skill-name>
(Or .codex/skills/, .cursor/skills/, .github/skills/, etc. — match the harness. In Claude Code this plugin targets .claude/skills/.)
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>"
status: active
---
# <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:
.claude/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 .claude/). 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 — the skdd CLI 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 it (plus trigger language like "Use when …")name matches the parent directory namereferences/).skills-registry.md