القائمة
How to write new skills for pikit — SKILL.md format, frontmatter, progressive disclosure, keeping content concise.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Recognizing context pressure before it degrades output quality.
Writing implementation plans — small testable steps, dependency ordering, upfront risk identification.
Evidence before claims, always — run verification commands and confirm output before making any completion or success claims.
Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.
Generate a structured changelog from git history — use when asked to create a changelog, release notes, or summarize what changed between versions/tags/branches.
How to write pikit workflow YAML files — steps, loops, branches, interpolation.
| name | skill-authoring |
| description | How to write new skills for pikit — SKILL.md format, frontmatter, progressive disclosure, keeping content concise. |
A skill is a directory under skills/ containing a SKILL.md file:
skills/
my-skill/
SKILL.md # Required: skill definition
references/ # Optional: supplementary material
examples.md
advanced.md
Every SKILL.md has two parts: YAML frontmatter and a markdown body.
---
name: my-skill
description: One-line description of what this skill provides.
---
# Skill Title
Body content here.
The body is the instruction set that gets loaded into context when the skill is activated.
Keep it under 100 lines. Context space is expensive. Every line should earn its place.
Guidelines:
Put supplementary material in a references/ subdirectory. This content is not loaded by default — it's available on demand for deeper dives.
Use references for:
name fieldwriting-tests, clean-code, skill-authoring