SKILLEMALL.ai
GitHub ↗ RU Sign in

CF manage-project

Research project management for medical manuscripts. Scaffold project structure, track writing progress across phases, maintain project memory files, generate submission checklists and backwards timelines. Commands: init, status, sync-memory, checklist, timeline.

Aperivue/medsci-skills Agent Skills author: Aperivue MIT 8 files body ≈ 2 453 tokens Open the sourcegithub.com↗ analyzed 33 h ago

Research project management for medical manuscripts.

As a process F 44/100 · Will not run — References files that are not bundled: templates/SSOT.yaml.template, scripts/init_project.py, scripts/validate_project_contract.py

GeneratorPersonal productivityOperations and projectstype 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
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
F
44/100
Will not run
References files that are not bundled: templates/SSOT.yaml.template, scripts/init_project.py, scripts/validate_project_contract.py
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
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: 8. 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: templates/SSOT.yaml.template
  • warning missing-ref reference to a missing file: scripts/init_project.py
  • warning missing-ref reference to a missing file: scripts/validate_project_contract.py
  • warning missing-ref reference to a missing file: scripts/migrate_project_to_ssot.py
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note edit-residue the text marks something as outdated (lines 20, 38, 56): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: templates/SSOT.yaml.template, scripts/init_project.py, scripts/validate_project_contract.py
  • 0Tools and files. 4 referenced file(s) missing: templates/SSOT.yaml.template, scripts/init_project.py, scripts/validate_project_contract.py
  • 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
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 34 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2453 tokens
  • 100Running it twice. Mutating operations check current state

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 263: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 34 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)
  • +4Reference files are cited in the instructions (2 of 5)

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