SKILLEMALL.ai
GitHub ↗ RU Sign in

BC digital-brain

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or mentions personal brand, content creation, network management, or voice consistency.

foryourhealth111-pixel/Vibe-Skills Agent Skills author: foryourhealth111-pixel Apache-2.0 39 files · 5 scripts body ≈ 1 672 tokens Open the sourcegithub.com↗ analyzed 30 h ago

This skill should be used when the user asks to "write a post", "check my voice", "look up contact", "prepare for meeting", "weekly review", "track goals", or…

As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

GeneratorMarketingtype 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%
82
Run on models
none yet
Process rating
C
59/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

    Medium and low: 1
    • medium Broad scope meta-agent-memory-dump identity/IDENTITY.md
      Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
      identity/IDENTITY.md

    Files scanned: 38. 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 59/100

    • 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
    • 30Running it twice. 6 mutating operations with no state check
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 58 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1672 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

    • +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
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +3Description length 243: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 58 items
    • +4Has examples (4 code blocks)

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