SKILLEMALL.ai
GitHub ↗ RU Sign in

AC promotion-review

Analyze promotion/review materials (述职/晋升材料) as an evaluator, identify issues and likely interview questions, then provide coaching advice. Supports text files, PDFs, and images (screenshots). Default output is Markdown file; HTML with Cloudflare R2 upload is optional. Use when user sends promotion documents, review materials, 述职材料, 晋升材料, or asks to review/analyze career advancement documents.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 1 133 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Analyze promotion/review materials (述职/晋升材料) as an evaluator, identify issues and likely interview questions, then provide coaching advice.

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

AnalyzerCloudflareWordPeople and hiringtype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
C
53/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

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: 4. 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 53/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
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 100Tools and files. No external tools needed
    • 100Steps. 69 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1133 tokens
    • 100Running it twice. No mutating operations
    • low 10 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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -5TODO / placeholder text left in the skill
    • -231 emoji in the instructions: noise for the model
    • +1No license
    • +2Single-language instructions
    • +3Description length 396: enough signal without eating the budget
    • +4Structure: 31 headings
    • +3Step-by-step instructions: 69 items
    • +4Has examples (3 code blocks)

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