SKILLEMALL.ai
GitHub ↗ RU Sign in

CC wiki-enrich

Fill in the per-paper TODO sections of research-wiki/papers/<slug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich wiki', 'fill paper TODOs', 'wiki body 補完', '把 paper 摘要寫進 wiki', 'research-wiki 自動填', or after a batch ingest that left papers/ as TODO scaffolds.

wanshuiyin/Auto-claude-code-research-in-sleep Claude Code author: wanshuiyin MIT 1 file body ≈ 4 016 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Fill in the per-paper TODO sections of research-wiki/papers/<slug>.md pages that literature-ingest skills leave as bare scaffolds. Use when user says 'enrich…

As a process C 50/100 · Has gaps — References files that are not bundled: ../shared-references/output-language.md

ProcedurePersonal productivitytype 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
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
76
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: ../shared-references/output-language.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
50
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: Auto-claude-code-research-in-sleep

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash(*)
    allowed-tools: Bash(*) Read Write Edit Glob Grep WebFetch

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../shared-references/output-language.md
  • note edit-residue the text marks something as outdated (lines 34, 104, 159): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ../shared-references/output-language.md
  • 0Tools and files. 1 referenced file(s) missing: ../shared-references/output-language.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 4016 tokens
  • 85Steps. 46 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (3 tags): a typed call is more reliable

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)
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 303: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 46 items
  • +3Output format is stated explicitly
  • +4Has examples (8 code blocks)

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