Revops
v1.0.0When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps...
⭐ 0· 100·0 current·0 all-time
byMario Karras@mariokarras
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (RevOps, lead lifecycle, lead scoring, routing rules, SLA templates) align with the included SKILL.md and reference docs. It is advisory in nature and does not request unrelated binaries, cloud credentials, or platform access.
Instruction Scope
SKILL.md is focused on designing processes, scoring, routing, and automation recipes. It explicitly asks the agent to read a local product-marketing-context.md file (if present) for context — this is relevant to RevOps tasks. The instructions do not direct the agent to read arbitrary system files, leak data to external endpoints, or require undisclosed secrets.
Install Mechanism
No install spec and no code files to execute; the skill is instruction-only. That minimizes disk writes and reduces execution risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. References to third-party systems (HubSpot, Salesforce, Calendly, Zapier, Clearbit) appear as implementation examples only and do not translate into requested secrets.
Persistence & Privilege
always is false and disable-model-invocation is false (default autonomous invocation allowed). This is normal for advisory skills and is not combined with any elevated credential or persistence requests here.
Assessment
This skill is an advisory RevOps playbook and appears internally consistent. Before installing, check whether your agent workspace contains a .agents/product-marketing-context.md (or .claude/...) and whether that file includes any sensitive secrets you don't want the skill to read — the skill will read it for context if present. Because it's an agent-invocable skill (default), the agent may call it autonomously; if you prefer to control invocation, disable autonomous skills in your agent settings. If you later plan to have the agent execute workflows in your CRM, you'll need separate integration skills/credentials — this skill itself does not request or store those credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk97826ggf7vw3twq2vtmy0pbg9836wp5
License
MIT-0
Free to use, modify, and redistribute. No attribution required.