codex-skill-authoring
Skill40 starsChanged 3 days agoApache-2.0View on GitHub
Use when creating, renaming, retrofitting, linting, or scaffolding repo-local Codex skills for hushh-research.
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- release-ios-appstoreSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 6 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with repo-context and docs-governance.
- Distinctive: line 49
Run the skill linter before changing the skill fleet so the current drift and coverage state are explicit.
- Very specific: line 52
Update the repo-context index, workflow packs, and agent-facing docs when an entrypoint or rename becomes canonical.
- Distinctive: line 55
Keep blocking versus advisory skill drift explicit.
- Very specific: line 56
When PR governance comment templates change, enforce them through skill_lint.py so stale public-comment headings such as Acknowledgment, …
- Very specific: line 57
Keep recurring SOPs short in skills and route durable detail to canonical docs or workflow packs.
- Very specific: line 58
Treat compact-kernel lint findings as blocking.
- Distinctive: line 61
When retrofitting a skill, scan the full skill body for duplicated rules, stale historical examples, and oversized decision trees.
- Distinctive: line 62
When a skill asks planning or operator questions, require research-backed question shape from the truth-first kernel: current truth, …
- Very specific: line 63
When skill or workflow changes alter docs homes, route through docs-governance and the docs/development/references.md classification model …
- Distinctive: line 64
When route governance changes alter required reads or checks, update the owning frontend, cache, voice, mobile, docs, and surface-map …
- Very specific: line 68
If the task begins with broad repo discovery or choosing the correct owner family, start with repo-context.
- Very specific: line 69
If the task is docs-home governance outside the skill system, use docs-governance.
- Distinctive: line 70
After skill creation or retrofit, hand off to the correct owner skill for the actual domain work.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Codex Skill Authoring Skill
Purpose and Trigger
- Primary scope:
codex-skill-authoring-intake - Trigger on creating or renaming repo-local skills, tightening the skill contract, adding skill tooling, or evolving the owner/spoke taxonomy.
- Avoid overlap with
repo-contextanddocs-governance.
Coverage and Ownership
- Role:
owner - Owner family:
codex-skill-authoring
Owned repo surfaces:
.agents/skills
Non-owned surfaces:
repo-contextdocs-governance
Do Use
- Creating new owner or spoke skills under
.agents/skills. - Enforcing the shared local skill contract,
skill.jsonmanifests, and workflow-pack contracts. - Scaffolding skills, manifests, and workflow packs and validating the fleet for drift, overlap, or orphaned surfaces.
Do Not Use
- Broad repo-orientation work that should start with
repo-context. - Product implementation or subsystem-specific work that already belongs to another owner skill.
- Docs-home governance outside the skill system itself.
Read First
.agents/skills/codex-skill-authoring/references/skill-contract.md.agents/skills/codex-skill-authoring/references/truth-first-operating-kernel.md.agents/skills/codex-skill-authoring/references/authoring-workflow.md.agents/skills/repo-context/references/index-contract.md
Workflow
- Run the skill linter before changing the skill fleet so the current drift and coverage state are explicit.
- Decide whether the work needs a new owner, a new spoke, or a tighter existing skill.
- Scaffold with
init_skill.pyusing explicit role, owner family, owned repo surfaces, task types, verification bundles, and optional workflow packs. - Update the repo-context index, workflow packs, and agent-facing docs when an entrypoint or rename becomes canonical. Read canonical
.agents/sources directly; verify actual host discovery separately. Do not generate per-host adapters or fleet copies. - For new owner skills or workflow-pack changes, run a second lint/audit pass after the edits instead of trusting the first clean run.
- For licensing, onboarding, subtree, CI, or branch-governance skill changes, do a third check from the canonical repo entrypoint before calling the taxonomy stable.
- Keep blocking versus advisory skill drift explicit. Only owner/workflow drift that weakens runtime, deploy, release, or test authority should block the core loop; metadata-only drift should stay advisory.
- When PR governance comment templates change, enforce them through
skill_lint.pyso stale public-comment headings such asAcknowledgment,Verification, or maintainer-onlyNextdo not re-enter generated templates. - Keep recurring SOPs short in skills and route durable detail to canonical docs or workflow packs. Skills should point to
runtime-db-fact-sheet.md, the data-plane contract, or a workflow playbook rather than duplicating long table inventories. - Treat compact-kernel lint findings as blocking; report owner lanes as
owner <skill-id>so the human-facing label matches the manifest role. - Enforce the truth-first operating kernel through deterministic smoke fixtures so skills, workflows, and agents do not slide back into blind premise acceptance.
- For industry-grade skills, prefer a compact operating kernel in
SKILL.mdplus focusedreferences/files for detailed gates, templates, and calibration rules. Do not let incident-specific fixes accumulate as repeated inline SOP unless they belong in deterministic scripts or a focused reference. - When retrofitting a skill, scan the full skill body for duplicated rules, stale historical examples, and oversized decision trees. Keep the main skill procedural; move reusable detail into references and executable logic into scripts.
- When a skill asks planning or operator questions, require research-backed question shape from the truth-first kernel: current truth, recommended path, risk if accepted blindly, decision needed, and recommended option first.
- When skill or workflow changes alter docs homes, route through
docs-governanceand thedocs/development/references.mdclassification model instead of inventing a parallel docs taxonomy. - When route governance changes alter required reads or checks, update the owning frontend, cache, voice, mobile, docs, and surface-map skills together so future agents see the same route contract cascade.
Handoff Rules
- If the task begins with broad repo discovery or choosing the correct owner family, start with
repo-context. - If the task is docs-home governance outside the skill system, use
docs-governance. - After skill creation or retrofit, hand off to the correct owner skill for the actual domain work.
- Route licensing skill work to
oss-license-governance, contributor setup skill work tocontributor-onboarding, and upstream/subtree sync skill work tosubtree-upstream-governance.
Required Checks
python3 .agents/skills/codex-skill-authoring/scripts/truth_first_smoke.py
python3 .agents/skills/codex-skill-authoring/scripts/compact_kernel_smoke.py
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.py
python3 .agents/skills/codex-skill-authoring/scripts/skill_fleet_audit.py --text
python3 .agents/skills/codex-skill-authoring/scripts/trigger_evals.py --text
python3 .agents/skills/codex-skill-authoring/scripts/init_skill.py --name example-owner --role owner --owner-family example-owner --owned-path README.md --task-type repo-orientation --verification-bundle example-owner --workflow-pack example-owner --dry-run
./bin/hushh agents audit
python3 -m py_compile .agents/skills/codex-skill-authoring/scripts/skill_lint.py .agents/skills/codex-skill-authoring/scripts/truth_first_smoke.py .agents/skills/codex-skill-authoring/scripts/init_skill.py .agents/skills/codex-skill-authoring/scripts/compact_kernel_smoke.py .agents/skills/codex-skill-authoring/scripts/skill_fleet_audit.py .agents/skills/codex-skill-authoring/scripts/trigger_evals.py .agents/skills/codex-skill-authoring/scripts/test_trigger_evals.pyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

