Pipeline Analyst
v1.0.0Expert AI agent specializing in pipeline analyst. From The Agency (github.com/msitarzewski/agency-agents).
⭐ 0· 57·0 current·0 all-time
by@zhouqkt
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (pipeline health, forecasting, MEDDPICC scoring) align with the provided SKILL.md/AGENTS.md/SOUL.md content. There are no unrelated requirements (no cloud credentials, no binaries) that conflict with the claimed purpose.
Instruction Scope
All runtime instructions are analytic and advisory (how to score deals, what to report). The skill does not instruct the agent to read system files, access unexpected endpoints, or exfiltrate data. It is somewhat high-level about data inputs — it assumes pipeline/CRM data will be provided but does not prescribe how; this means real-world use will require you to supply data or grant CRM access outside the skill.
Install Mechanism
No install spec and no code files — nothing is written to disk or downloaded. This is the lowest install risk.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate to an instruction-only analytics agent.
Persistence & Privilege
Defaults (not always-included, user-invocable, model invocation allowed) are used. The skill does not request permanent presence or system-wide configuration changes.
Assessment
This skill is internally coherent and low-risk as packaged: it's only documentation/instructions for pipeline analysis and does not include code or request credentials. Before using it in your agent: 1) Decide how you will provide pipeline/CRM data — the skill assumes such data but does not include connectors; avoid pasting full production credentials into chat. 2) If you integrate the agent with a CRM/BI system, use scoped, least-privilege API keys and test with anonymized or sample data first. 3) Monitor any agent actions that access external systems when you enable autonomous invocation. 4) If you need a connector added, review that connector's install/permissions separately — the skill itself does not perform installs or network calls.Like a lobster shell, security has layers — review code before you run it.
agencyvk97cy5j43a76dcg8j4278r9ne984q1f2ai-agentsvk97cy5j43a76dcg8j4278r9ne984q1f2latestvk97cy5j43a76dcg8j4278r9ne984q1f2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📊 Clawdis