SKILLEMALL.ai
GitHub ↗ RU Sign in

FC workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.

Blockedguard blocked the skill: signs of malicious behaviour
specstoryai/getspecstory Claude Code author: specstoryai 19 files · 9 scripts body ≈ 1 061 tokens Open the sourcegithub.com↗ analyzed 4 d ago

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and…

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmentAI and agentstype 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
F
42/100
safety, quality, tests
Safety 60%
10
Quality 40%
89
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
Guard blocked this skill: critical findings below. Do not install it until the author fixes them.

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Secrets in code
If you install

The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

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. Remove the critical guard findings (secrets, dangerous commands, hidden instructions): while they stand the skill is blocked and cannot grade above F.
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 · 8

  • critical Secrets in code secret-github-token scripts/lib/patterns.mjs:187
    GitHub token
    //   ghp_…B4a      GitHub token (ghp_/gho_/ghu_/ghs_/ghr_)
Medium and low: 7
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Write AskUserQuestion
  • low Secrets in code secret-aws-key scripts/lib/patterns.mjs:186
    AWS access key ID (placeholder value)
    //   AKIA…PLE                          AWS access key id
    placeholder
  • low Secrets in code secret-high-entropy-token scripts/lib/patterns.mjs:187
    High-entropy token-like string (may be an id, hash or a credential)
    //   ghp_…B4a      GitHub token (ghp_/gho_/ghu_/ghs_/ghr_)
  • low Secrets in code secret-slack-token scripts/lib/patterns.mjs:189
    Slack token (placeholder value)
    //   xoxb…hij                    Slack token
    placeholder
  • low Secrets in code secret-high-entropy-token scripts/lib/patterns.mjs:191
    High-entropy token-like string (may be an id, hash or a credential) (placeholder value)
    //   AIza…stu       Google API key
    placeholder
  • low Secrets in code secret-google-key scripts/lib/patterns.mjs:191
    Google API key (placeholder value)
    //   AIza…stu       Google API key
    placeholder
  • low Secrets in code secret-password-literal scripts/lib/patterns.mjs:194
    Hard-coded password / key literal (may be an example)
    //   API_KEY=hunt…er2 / "token": "abc12345"  assignment with a secret-named key

Files scanned: 18. 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 61/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 17 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1061 tokens

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
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 547: enough signal without eating the budget
  • +4Structure: 5 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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