Validate GitHub issues by tracing claims and scoring complexity via a Fable 5 subagent.
npx skills add https://github.com/richkuo/rk-skills --skill fable-validate
Please help me install this Agent Skill. Skill: fable-validate Source: https://github.com/richkuo/rk-skills/tree/main/skills/fable-validate Command: npx skills add https://github.com/richkuo/rk-skills --skill fable-validate
This skill solves the problem of unreliable or poorly defined GitHub issues by delegating the validation process to a specialized Fable 5 subagent, ensuring that every issue is technically feasible and well-scoped before work begins.
Trigger the validation process for a specific issue by typing /fable-validate followed by the issue number in your chat session.
High-intent search queries and answers about installing and using this skill.
Validating GitHub issues automatically involves delegating claim tracing and architectural consistency checks to a Fable 5 subagent. It verifies code references and complexity scores in read-only mode without modifying the file system.
Automated issue fact-checking traces claims made in GitHub issues against the actual codebase to verify their accuracy and architectural consistency. This ensures every issue is technically feasible and well-scoped before work begins.
Yes, you can validate GitHub issues without modifying your repository. The skill operates in a read-only mode via a subagent harness, preventing accidental file edits or repository changes during the validation phase.
To trigger GitHub issue validation, type the /fable-validate command followed by the specific issue number in your chat session. This initiates the validate-issue procedure and returns a structured verdict.
Yes, automated complexity scoring assigns a score from C0 to C100 to GitHub issues and determines if a Fable plan is required. This helps evaluate the technical scope and feasibility before development starts.
The main limitation of using a read-only subagent for issue tracking is that it cannot execute file edits or apply repository changes. It requires a read-only subagent harness strictly to return a structured verdict for main agent action.
sunzcdevApply type, effort, priority, and area labels to GitHub issues.
CornjebusCoordinate multi-agent code reviews for GitHub pull requests.
richkuoTrace GitHub issue claims to specific code locations and evaluate solution feasibility.
richkuoDraft GitHub issues via a read-only Fable 5 subagent with duplicate checks and complexity scoring.
