AC paper-contribution-helper
Build and use a modular paper contribution helper from target papers, research fields, years, and paper sources. Use when Codex needs to help researchers package a paper's contribution, diagnose novelty risk, prepare reviewer defenses, or build a portable self-contained helper from reference papers.
As a process C 63/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Exfiltration
intent-browser-credential-storereferences/base_delta/workflow_knowledge_base_build.md:62Accesses a browser credential / cookie store (documentation of a security skill)This step writes anonymous reusable knowledge under `.delta-contribution-reframer/references/` and updates project-local state so future skill use in this project does not depend on absolute project p
security skill -
low Concealment
en-hide-from-userassets/domain-skill-template/SKILL.template.md:70Instruction to hide actions from the user ("do not tell the user <a claim>" — honesty guidance, not concealment; documentation of a security skill)Do not tell the user that a project-internal corpus cannot be analyzed merely because API/acpx/local-command automation is missing. Continue locally or name a concrete non-backend blocker, such as unr
honesty claimsecurity skill -
low Concealment
en-hide-from-userSKILL.md:86Instruction to hide actions from the user ("do not tell the user <a claim>" — honesty guidance, not concealment; documentation of a security skill)- Never tell the user that a project-internal corpus cannot be analyzed merely because API/acpx/local-command automation is missing. Continue locally or name a concrete non-backend blocker, such as un
honesty claimsecurity skill
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2158 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Output format is not stated: the model decides each time
- -33 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 300: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (11 of 13)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.