epic-create
epic-create is an Issues & backlog tracking skill for AI agents, published by neomjs in the neo repository on GitHub. Skillspace rates epic-create C (74/100) and it passed the safety scan; the rating is based on static analysis only.
Authoritative protocol for authoring an Epic body — the creation-side dual of `ticket-create` + entry partner of `epic-review`/`epic-resolution`. Enforces: epic body = problem-scope + intended-solution (NOT pseudo-subs / ACs); ACs live in the SUB tickets; subs are LINKED via `update_issue_relationship` + added incrementally; the body MUST NOT hardcode a sub-list (it stales out → FAIL). Triggers: before creating an Epic (a parent issue labeled `epic`) via `create_issue`, or before decomposing one into sub-tickets.
- Grade
- C
- Quality
- 74 / 100
- Safety
- Passed
- GitHub stars
- 3,234
Unproven: rated by static analysis only, not yet compared head-to-head.
Not launch-quality. It is graded C with a clean safety verdict, but our quality filters exclude it: it looks written only for the repository it lives in. So it is not in our launch-quality set, the skills our MCP server searches and recommends. How launch-quality is decided
Our two independent classifiers differ on this skill's category, so treat the placement as provisional.
This rating describes the version of the repository we crawled; it may have changed since, so go by its current files.
Our review
- Architecture
- 100 / 100
- Maturity
- Structured: ships references or scripts
- Security scan
- No issues found
- License
- MIT
- Adoption
- Adopted by 0 other repositories, in 0 collections
Not checked yet
- Not judged on the rubric yet (not a contender in its category)
- No blind task eval yet
- Scope (portable / vendor / repo-internal) not assessed; only the top of each category is read for scope
- Sibling files (scripts, references) not fetched; security scan covers SKILL.md only
Skillspace indexes and rates this skill; it does not host or endorse it. Run third-party skills at your own risk.