SKILLEMALL.ai
GitHub ↗ RU Sign in

AC humanize

Edit or audit prose for generic AI patterns while preserving voice, meaning, uncertainty, and format. Use when writing sounds synthetic, repetitive, over-polished, or unlike its author.

tushaarmehtaa/tushar-skills Agent Skills author: tushaarmehtaa 4 files body ≈ 1 300 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Edit or audit prose for generic AI patterns while preserving voice, meaning, uncertainty, and format.

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

AnalyzerWriting and documentsData and analyticsSales and CRMtype 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
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: humanize (tushaarmehtaa/tushar-skills)

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

    • 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
    • 30Running it twice. 4 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 29 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1300 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

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 185: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 29 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

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