SKILLEMALL.ai
RU Sign in

B create-github-issues-feature-from-implementation-plan

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.

github/awesome-copilot Agent Skills author: github MIT 1 file body ≈ 188 tokens open source ↗ analyzed 19 h ago

Create GitHub Issues from implementation plan phases using featurerequest.yml or chorerequest.yml templates.

GeneratorGitHubtype and topics are labelled automatically from the skill text
Runs in: GitHub Copilot / VS Code Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
B
86/100
Overall score
Safety 60%
100
Quality 40%
65
Tests bonus
0

The same skill appears in 1 more place: RA-Skills

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): it is the main trigger signal.
  2. Add evals/evals.json with 4–6 real requests and expected answers: the full check will then use your cases instead of a model draft.
  3. Add a spec.yaml with triggers and assertions (skilltest init): the behaviour contract for CI.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Lint

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process maturity 63/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 11 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 188 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 110: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 4 headings
  • +3Step-by-step instructions: 11 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.