SKILLEMALL.ai
GitHub ↗ RU Sign in

AA revops

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 6 files body ≈ 3 700 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation.

As a process A 85/100 · Runs to the end — weak spots: running it twice

ProcedureData and analyticsInfrastructureSales 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
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
84
Run on models
none yet
Process rating
A
85/100
Runs to the end
Running it twice w 4
30
Failures and branches w 10
50
When it triggers w 12
70
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: revops (sickn33/agentic-awesome-skills)

How to improve

    For the model run — optional
    • 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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "date_added"

    Process rating: all ten parameters 85/100

    • 30Running it twice. 9 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 97 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3700 tokens
    • 100Progress reporting. Reports progress
    • low 16 top-level sections: this looks like several domains in one skill
    • medium 6 test cases, all positive: not one "should refuse" or "should ask first"
    • low No test case covers injection arriving through data

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 210: enough signal without eating the budget
    • +4Structure: 45 headings
    • +3Step-by-step instructions: 97 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (4 of 4)

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