SKILLEMALL.ai
GitHub ↗ RU Sign in

AC feedback-triage

This skill should be used when the user asks to "process beta reader feedback", "alpha reader feedback", "feedback round", "synthesize reader feedback", "reader notes", "beta feedback", "reader readiness check", "review copy", "send the draft to readers", "share with readers who don't use GitHub", "triage the reader panel", or wants to collect, reconcile, and act on external reader feedback for a story project. NOT for rounds with a professional editor (use editorial-review), or for checking a manuscript is ready to query or publish (use submission or publishing).

danjdewhurst/story-skills Agent Skills author: danjdewhurst MIT 3 files body ≈ 2 802 tokens Open the sourcegithub.com↗ analyzed 5 d ago

This skill should be used when the user asks to "process beta reader feedback", "alpha reader feedback", "feedback round", "synthesize reader feedback"…

As a process C 58/100 · Has gaps — References files that are not bundled: templates/github/review-copy.yml, templates/github/ISSUE_TEMPLATE/manuscript-note.yml

ProcedureGitHubAI and agentsFinancePeople and hiringtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
58/100
Has gaps
References files that are not bundled: templates/github/review-copy.yml, templates/github/ISSUE_TEMPLATE/manuscript-note.yml
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: templates/github/review-copy.yml
  • warning missing-ref reference to a missing file: templates/github/ISSUE_TEMPLATE/manuscript-note.yml

Process rating: all ten parameters 58/100

Will not run. References files that are not bundled: templates/github/review-copy.yml, templates/github/ISSUE_TEMPLATE/manuscript-note.yml
  • 0Tools and files. 2 referenced file(s) missing: templates/github/review-copy.yml, templates/github/ISSUE_TEMPLATE/manuscript-note.yml
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 10 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 40 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2802 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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

  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 11 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 570: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)

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