SKILLEMALL.ai
GitHub ↗ RU Sign in

BC rebuttal

Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says "rebuttal", "reply to reviewers", "ICML rebuttal", "OpenReview response", or wants to answer external reviews safely.

wanshuiyin/Auto-claude-code-research-in-sleep Claude Code author: wanshuiyin MIT 1 file body ≈ 3 945 tokens Open the sourcegithub.com↗ analyzed 5 h ago

Workflow 4: Submission rebuttal pipeline.

As a process C 58/100 · Has gaps — References files that are not bundled: ../shared-references/reviewer-backends.md

ProcedureSoftware developmentOperations and projectsInfrastructuretype 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
B
90/100
safety, quality, tests
Safety 60%
95
Quality 40%
83
Run on models
none yet
Process rating
C
58/100
Has gaps
References files that are not bundled: ../shared-references/reviewer-backends.md
Tools and files w 18
0
When it triggers w 12
20
Result and completion w 14
40
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 Grep Glob Write Edit Skill mcp__antigravity__antigravity mcp__antigravity__antigravity-reply mcp__grok__grok mcp__grok__grok-reply mcp__claude-review__review mcp__claude-re

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/reviewer-backends.md

Process rating: all ten parameters 58/100

Will not run. References files that are not bundled: ../shared-references/reviewer-backends.md
  • 0Tools and files. 1 referenced file(s) missing: ../shared-references/reviewer-backends.md
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 128 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3945 tokens
  • 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

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 4 example trigger phrases
  • +3Description length 319: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 128 items
  • +4Has examples (5 code blocks)

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