SKILLEMALL.ai
RU Sign in

AA standup-report

Turn raw scratch notes — Slack threads, daily journal lines, half-written bullets — into a clean Yesterday / Today / Blockers daily standup, or a weekly Wins / Lowlights / Next-Week summary. Trigger when the user says "write my standup", "summarize my day", "weekly status report", "turn my notes into a standup", or "draft a daily standup". Tunes tone to the audience (eng team, cross-functional, manager 1:1) and tags blocker owners.

genspark Agent Skills author: Genspark 1 file body ≈ 1 554 tokens Open the sourcegenspark.ai↗ analyzed 2 d ago

As a process A 86/100 · Runs to the end — weak spots: running it twice, progress reporting

GeneratorSlackData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Genspark 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
A
86/100
Runs to the end
Progress reporting w 2
0
Running it twice w 4
30
Result and completion w 14
60
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 86/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 3 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 36 steps
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 7 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1554 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)
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 5 example trigger phrases
    • +3Description length 435: enough signal without eating the budget
    • +4Structure: 8 headings
    • +3Step-by-step instructions: 36 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)

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