SKILLEMALL.ai

CD retro

Ретро недели для штаба. Читает задачи всех отделов, собирает что сделано, что застряло и что повторяется, пишет tasks/retro-<ГГГГ>-W<NN>.md в штабе. Применять по «ретро», «что было за неделю», «итоги недели», «retro».

serejaris/personal-corp-os Claude Code author: serejaris MIT 3 files body ≈ 869 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Ретро недели для штаба.

As a process D 48/100 · Unfinished process — References files that are not bundled: ../../corp-learn/tasks/<файл>.md

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
D
48/100
Unfinished process
References files that are not bundled: ../../corp-learn/tasks/<файл>.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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 description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../corp-learn/tasks/<файл>.md

Process rating: all ten parameters 48/100

Will not run. References files that are not bundled: ../../corp-learn/tasks/<файл>.md
  • 0Tools and files. 1 referenced file(s) missing: ../../corp-learn/tasks/<файл>.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Failures and branches. 5 branches
  • 100Steps. 18 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 869 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 217: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 18 items
  • +4Has examples (1 code blocks)

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