SKILLEMALL.ai
GitHub ↗ RU Sign in

AA timesheet-payroll-check

Use when the user asks to check a payroll run against the timesheet and the shift schedule, or says: сверь табель с графиком и зарплатой, проверь начисления за месяц, найди оплаченные несуществующие смены. Do not use for changing payroll: this skill only prepares the discrepancies for a person.

skillemall-templates Agent Skills 1 file body ≈ 1 343 tokens analyzed 31 h ago

Use when the user asks to check a payroll run against the timesheet and the shift schedule, or says: сверь табель с графиком и зарплатой, проверь начисления…

As a process A 97/100 · Runs to the end — no weak spots found

AnalyzerFinancetype 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%
95
Quality 40%
89
Run on models
none yet
Process rating
A
97/100
Runs to the end
Inputs and preconditions w 11
70
Tools and files w 18
100
Steps w 15
100
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-broad-allowed-tools SKILL.md:1
      Broad tool permissions pre-approved: Bash
      allowed-tools: Read Bash

    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 97/100

    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 13 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100When it triggers. States when to use and when not to
    • 100Failures and branches. 4 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1343 tokens
    • 100Running it twice. No mutating operations
    • 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
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 295: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (1 code blocks)
    • +1License stated

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