Funnels Knowledge Management
Provides a protocol for documenting and managing marketing funnel logic to prevent configuration drift.
Install
mkdir -p .claude/skills/funnels-knowledge-management && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15582" && unzip -o skill.zip -d .claude/skills/funnels-knowledge-management && rm skill.zipInstalls to .claude/skills/funnels-knowledge-management
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Agent protocol for reading, interpreting, and updating marketing funnel documentation.Key capabilities
- →Retrieve information from funnel documentation
- →Consult specific funnel documents for data flow changes
- →Escalate unclear or missing information to a human
- →Update relevant funnel documents with new knowledge
- →Create new funnel documents using a standard template
How it works
The skill consults an index for active funnels, then accesses specific funnel documents for information, escalating to a human when documentation is unclear or missing.
Inputs & outputs
When to use Funnels Knowledge Management
- →Updating funnel documentation
- →Documenting CRM pipeline mapping
- →Verifying integration flows
- →Managing traffic source details
About this skill
Funnels Knowledge Base Skill
This skill governs how you interact with funnel documentation located in plans/knowledge/funnels/. This applies whenever you are tasked with designing, troubleshooting, or integrating logic related to any funnel (e.g., Eventbrite, GoHighLevel, Facebook Ads, Instantly).
1. Information Retrieval
- Always consult
plans/knowledge/funnels/index.mdto see the list of active funnels before assuming a system flow. - Consult the specific funnel document (e.g.,
ai-clinic.md,ai-fluency.md) when making changes that interact with that funnel's data flow.
2. Mandatory Human Escalation (No Guessing)
When working on a funnel integration, if any part of the flow, system trigger, technical integration, or CRM pipeline mapping is unclear, ambiguous, or missing from the documentation:
- DO NOT ASSUME OR GUESS.
- You MUST refer back to the human.
- Pause your execution and immediately use the
notify_usertool (or ask directly) with specific questions to clarify the missing information. - If a tag name, pipeline name, or sequence detail is unspecified in the documentation, ask the human for the exact expected value.
3. Knowledge Persistence
Once the human provides the answer or clarification:
- You MUST update the relevant funnel document in
plans/knowledge/funnels/to persist this new knowledge. - If it's a new funnel altogether, create a new document using the standard template and link it in
plans/knowledge/funnels/index.md. - Preserve the standard template sections (Overview, Traffic Sources, Entry Points, Flow, Integrations, CRM Mapping, Status).
When not to use it
- →When any part of the flow, system trigger, technical integration, or CRM pipeline mapping is unclear, ambiguous, or missing from the documentation
Limitations
- →The skill will not assume or guess missing information
- →The skill requires human intervention for unclear documentation
- →Documentation updates must preserve standard template sections
How it compares
This skill enforces a structured protocol for managing funnel documentation, including mandatory human escalation for ambiguities, which differs from ad-hoc documentation practices.
Compared to similar skills
Funnels Knowledge Management side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Funnels Knowledge Management (this skill) | 0 | 2mo | No flags | Intermediate |
| prd | 11 | 6mo | No flags | Intermediate |
| wiki-onboarding | 4 | 4mo | No flags | Beginner |
| spec-writing | 1 | 1mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by stelios12312312
View all by stelios12312312 →You might also like
prd
github
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
wiki-onboarding
microsoft
Generates two complementary onboarding guides — a Principal-Level architectural deep-dive and a Zero-to-Hero contributor walkthrough. Use when the user wants onboarding documentation for a codebase.
spec-writing
jeremylongshore
Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
aico-pm-prd-writing
yellinzero
|
lisa-prd-backlink
CodySwannGT
Update a source PRD with an always-written, machine-readable `## Tickets` (alias `## Generated Work`) section linking back to every work item created from it. Each entry carries a parseable ref + URL + type + parent token so the generated child set is readable without scraping prose. Vendor-aware on
product-spec-builder
zinohome
你是一个**毒舌产品经理**，负责需求收集、产品文档编写和迭代更新。你的核心特点是：