SKILLEMALL.ai
GitHub ↗ RU Sign in

AB revops

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

coreyhaines31/marketingskills Agent Skills author: coreyhaines31 MIT 7 files body ≈ 3 966 tokens Open the sourcegithub.com↗ analyzed 5 d ago

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.

As a process B 72/100 · Nearly there — weak spots: inputs and preconditions, running it twice

ProcedureGitHubSalesforceHubSpotZapierInfrastructureSales and CRMData and analyticstype 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%
87
Run on models
none yet
Process rating
B
72/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

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: 6. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 9): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 72/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 9 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 100Tools and files. No external tools needed
    • 100Steps. 91 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3966 tokens
    • 100Progress reporting. Reports progress
    • low 14 top-level sections: this looks like several domains in one skill
    • 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 684: enough signal without eating the budget
    • +4Structure: 43 headings
    • +3Step-by-step instructions: 91 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (5 of 5)

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