GitHub
codex-delegation
How to delegate implementation tasks to Codex workers via MCP. Use when executing tasks that require code implementation by GPT Codex workers.
☆ 0View skill
DUTSTECH AI Skills
GitHub ↗Browse published AI skills maintained by DUTSTECH. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
7Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
verification-rules
4-layer verification system for task completion. Use when verifying that a task has been fully completed before marking it done.
☆ 0View skill
GitHub
spec-workflow
Spec-driven development workflow for building features with research, requirements, design, and task phases
☆ 0View skill
GitHub
review-criteria
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
☆ 0View skill
GitHub
communication-style
Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.
☆ 0View skill
GitHub
delegation-principle
Core principle that the main agent is a coordinator, not an implementer. All work must be delegated to subagents.
☆ 0View skill
GitHub
reality-verification
Detect fix vs add goals, diagnose failures before work, verify fixes after. Ensures "fix X" specs actually fix X.
☆ 0View skill
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.