Arnie016/codex-prompt-templates / skills/automation-skill-forge
automation-skill-forge
VerifiedTurn automation runs into one or more specific Codex skill candidates. Use when an automation should produce reusable skills, stronger prompts, trend workflows, GitHub-ready skill artifacts, or generated-skill naming rules. Triggers: automation to skill, make this into a skill, generated skill pack, many skills from GitHub repos, trend-backed skill, skill naming regex. Skip when the task only needs a one-off fix or a broad brainstorm.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.8 KB |
SKILL.md
View on GitHub---
name: automation-skill-forge
description: >
Turn automation runs into one or more specific Codex skill candidates. Use
when an automation should produce reusable skills, stronger prompts, trend
workflows, GitHub-ready skill artifacts, or generated-skill naming rules.
Triggers: automation to skill, make this into a skill, generated skill pack,
many skills from GitHub repos, trend-backed skill, skill naming regex. Skip
when the task only needs a one-off fix or a broad brainstorm.
---
# Automation Skill Forge
Goal: turn recurring automation work and GitHub/source research into sharp,
non-overlapping Codex skill candidates or a clear decision not to create any.
## Naming Regex
Generated skills from this automation must use:
```regex
^auto-skill-(research|build|review|audit|ops|safety|trend)-[a-z0-9]+(?:-[a-z0-9]+){1,4}$
```
Format: `auto-skill-<mode>-<domain>-<artifact>`.
Examples:
- `auto-skill-trend-agentic-disease-intake`
- `auto-skill-safety-mcp-secret-guard`
- `auto-skill-build-github-repo-radar`
## Workflow
1. Read automation memory and the current workspace index first.
2. Read `references/maintenance-automation-scope.md` for the full agency model.
3. Choose a primary aim: research, build, review, audit, ops, safety, or trend.
4. Gather compact evidence with `rg`, manifests, README/docs, and exact source files.
5. For multiple local source clones, use
`$auto-skill-build-source-pattern-synthesis` to cluster workflow patterns
before writing skill files.
6. Create as many useful non-overlapping skills as the evidence justifies.
7. Move broad catalogs or long examples into references.
8. Validate each new or changed skill with `$skill-quality-gate`.
## Skill Candidate Contract
```md
Name:
Regex match:
Generated by:
Aim:
Trigger:
Inputs:
Workflow:
Commands:
References:
Skip when:
Validation:
Useful end goal:
```
## Command Defaults
- Search: `rg`, `rg --files`, exact symbols, package manifests.
- Repo scan: `scripts/repo_snapshot.sh <repo>` and `scripts/token_budget.sh <repo>` when available.
- Validation: `scripts/skill_audit.sh plugins/codex-supercharge/skills` and `quick_validate.py`.
- GitHub packaging: prepare files, docs, validation output, and commit-ready notes only; do not publish unless asked.
## Trend Guardrail
Use trend signals to choose domains, not to invent claims. Current trend-backed
skill ideas must cite source/date and include a safety or usefulness gate.
Read `references/automation-skill-patterns.md` and
`references/maintenance-automation-scope.md` before creating generated skills
or broad skill batches.
## Validation
- Every generated skill name matches the automation regex unless promoted to a stable first-class name.
- Each candidate has a trigger, skip condition, workflow, references, and validation.
- Broad catalogs or examples are moved into references before installation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |