SKILLEMALL.ai
GitHub ↗ RU Sign in

BC workflow

Project workflow for PRDs, task tracking, changelog sync, and documentation updates. Use for any non-trivial task that spans multiple steps, touches several files, changes architecture, or needs project tracking updates. Also activates with @update to sync task.md, changelog.md, and files.md after completing work.

The skillemall take

Promises to automate multi-step workflows: PRD sync, task tracking, changelog and docs updates. Triggers on complex tasks and @update command.

Contains 536 tokens, no lint errors. Quality score 80, process score 58. No critical findings. Not tested in sandbox or on models. Supports many platforms from Claude to DeepSeek.

Works for multi-file operations, but without execution examples it's hard to predict real-world behavior. Worth installing if your project already has task.md and changelog.md structure—the skill just keeps them in sync.

waynesutton/markdown-site Agent Skills author: waynesutton 1 file body ≈ 536 tokens Open the sourcegithub.com↗ analyzed 12 h ago

Project workflow for PRDs, task tracking, changelog sync, and documentation updates.

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

ProcedureWriting and documentstype 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
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

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

    ✓ No critical or high findings

    Files scanned: 1. 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 58/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
    • 55Failures and branches. 1 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 39 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 536 tokens
    • 100Progress reporting. Reports progress

    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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 315: enough signal without eating the budget
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 39 items

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