SKILLEMALL.ai

B react19-source-patterns

Reference for React 19 source-file migration patterns, including API changes, ref handling, and context updates.

github/awesome-copilot Agent Skills author: github MIT 2 files body ≈ 448 tokens open source ↗ analyzed 14 h ago

Reference for React 19 source-file migration patterns, including API changes, ref handling, and context updates.

IntegrationSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
B
88/100
Overall score
Safety 60%
100
Quality 40%
70
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: 2. 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 36/100

  • 0Steps. Prose only: no discrete steps
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 448 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 112: 120–800 characters recommended
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 4 headings
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (1 of 1)

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