SKILLEMALL.ai
GitHub ↗ RU Sign in

AB user-thoughts

Persist user decisions and project constraints to mdbase across sessions. Trigger on /user-thoughts or /ustht, or when the user discusses architecture, tech stack, rules, UI/UX, or project memory.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 24 files body ≈ 2 336 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Persist user decisions and project constraints to mdbase across sessions.

As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

ProcedureDesignAI and agentsOperations and projectstype 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
A
93/100
safety, quality, tests
Safety 60%
93
Quality 40%
93
Run on models
none yet
Process rating
B
66/100
Nearly there
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
This is a copy of a skill from another catalog; the rating counts the canonical one: user-thoughts (sickn33/agentic-awesome-skills)

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

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

    ✓ No critical or high findings

    Medium and low: 3
    • medium Broad scope meta-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: bash
      allowed-tools: read write bash
    • low Concealment en-hide-from-user references/safety.md:61
      Instruction to hide actions from the user (negated — the text forbids it)
      Processed raw files are retained for traceability. Dimension files should be appended or marked deprecated; do not silently delete user history.
      negated
    • low Concealment en-hide-from-user SKILL.md:230
      Instruction to hide actions from the user (negated — the text forbids it)
      - Never silently delete dimension files; mark deprecated content unless the user explicitly asks for deletion.
      negated

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "tools"
    • note frontmatter-key unknown frontmatter key "risk"
    • note edit-residue the text marks something as outdated (lines 181, 209): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 66/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
    • 30Running it twice. 8 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 73 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2336 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 17 top-level sections: this looks like several domains in one skill

    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
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 196: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 73 items
    • +4Has examples (2 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)
    • +3All 9 scripts are documented
    • +1License stated

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