CD research-repo
Scaffolds or audits an entire research-project repository organized around its source library. Use when the user starts, structures, organizes, or reviews a project, including "set up a research repo", "how should I structure/organize this project", "initialize my sources folder", "new paper or literature-review project", "audit my repo structure", "is my sources folder set up right", or "check my project layout". Builds the source spine, original PDFs, tracked Markdown conversions, drop zone, bibliography, intake pipeline, and suitable analysis, manuscript, and review folders, or audits what is present, partial, or missing. Single-PDF intake goes to process-source, replication packages to replication-package.
Scaffolds or audits an entire research-project repository organized around its source library.
As a process D 37/100 · Unfinished process — References files that are not bundled: scripts/convert-sources.sh
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5375 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/convert-sources.sh
Process rating: all ten parameters 37/100
- 0Tools and files. 1 referenced file(s) missing: scripts/convert-sources.sh
- 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
- 30Running it twice. 11 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 5375 tokens
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
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 7 example trigger phrases
- +3Description length 719: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.