القائمة
Manage revenue operations and CRM workflows including lead lifecycle, scoring, routing, pipeline configuration, handoff, enrichment, and community-led revenue motions.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Schedule, create, and manage social media posts on Instagram and LinkedIn using the Buffer GraphQL API. Use when the user wants to publish content, schedule posts, check scheduled posts, list connected channels, or create content ideas on Buffer.
Research SEO opportunities through audits, keyword discovery, traffic validation, and site architecture analysis.
Maintains and applies brand identity across all content operations. Ensures every output aligns with the personal brand's voice, values, and visual identity.
MCP skill for canva. Provides 23 tools: upload-asset-from-url, upload-asset-from-file, resolve-shortlink, search-designs, get-design, get-design-pages, get-design-content, get-presenter-notes, import-design-from-url, merge-designs, export-design, get-export-formats, create-folder, move-item-to-folder, list-folder-items, search-folders, comment-on-design, list-comments, list-replies, reply-to-comment, generate-design, create-design-from-candidate, list-brand-kits
Plan ads, generate ad creative, and configure paid acquisition measurement. Use for paid campaign setup and tracking.
Generate growth ideas and low-cost marketing approaches. Use for campaign ideation, growth planning, and free-tool strategy exploration.
| name | revenue-manager |
| description | Manage revenue operations and CRM workflows including lead lifecycle, scoring, routing, pipeline configuration, handoff, enrichment, and community-led revenue motions. |
| metadata | {"version":"1.0.0"} |
Bundle with tasks: revops, crm
Source skills from: marketingskills (revops, community-marketing)
cd skills/revenue-manager
uv sync # install dependencies (first time only)
cd skills/revenue-manager
uv run python scripts/revenue.py <command> [options]
| Command | Description |
|---|---|
revops | Revenue operations task - lead lifecycle, scoring, routing, pipeline |
crm | CRM configuration task - community marketing and ambassador programs |
| Flag | Description | Default |
|---|---|---|
--input <dir> | Input directory | ./input |
--output <dir> | Output directory | ./output |
--device <type> | Processing device: auto, cpu, cuda | auto |
# Run RevOps task with defaults
uv run python scripts/revenue.py revops
# Run with custom input/output
uv run python scripts/revenue.py revops --input ./data --output ./results
# Run CRM (Community Marketing) task
uv run python scripts/revenue.py crm --input ./input --output ./output
Revenue operations task for lead lifecycle management, scoring, routing, and pipeline configuration.
When you run uv run python scripts/revenue.py revops, it creates these deliverables in the output directory:
| Stage | Entry Criteria | Exit Criteria | Owner |
|---|---|---|---|
| Subscriber | Opts in to content | Provides company info or shows engagement | Marketing |
| Lead | Identified contact with basic info | Meets minimum fit criteria | Marketing |
| MQL | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing |
| SQL | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) |
| Opportunity | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) |
| Customer | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt |
| Evangelist | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing |
An MQL requires both fit and engagement:
| Metric | Formula | Benchmark |
|---|---|---|
| Lead-to-MQL rate | MQLs / Total leads | 5-15% |
| MQL-to-SQL rate | SQLs / MQLs | 30-50% |
| SQL-to-Opportunity | Opportunities / SQLs | 50-70% |
| Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal |
| Win rate | Closed-won / total opportunities | 20-30% |
Community marketing task for strategy, ambassador programs, and community-led growth.
When you run uv run python scripts/revenue.py crm, it creates these deliverables in the output directory:
The strongest communities are built around who members are or aspire to be — not around your product. Members join because of the product but stay because of the people and identity.
Examples:
Every community touchpoint should answer: What does the member get from this?
Members join → get value → engage → create content/help others
↑ ↓
←←←←← new members discover the community ←←
| Platform | Best For | Watch Out For |
|---|---|---|
| Discord | Developer, gaming, creator communities; real-time chat | High noise, hard to search, onboarding friction |
| Slack | B2B / professional communities; familiar to SaaS buyers | Free tier limits history; feels like work |
| Circle | Creator or course-based communities; clean UX | Less organic discovery; requires driving traffic |
| High-volume public communities; SEO benefit | You don't own it; moderation is hard | |
| Facebook Groups | Consumer brands; older demographics | Declining organic reach; algorithm dependent |
| Forum (Discourse) | Long-form technical communities; SEO-rich | Slower velocity; higher effort to post |
Track these signals weekly:
Warning signs:
output/
├── revops/
│ ├── lifecycle-stage-definitions.md
│ ├── scoring-specification.md
│ ├── routing-rules.md
│ ├── pipeline-configuration.md
│ └── metrics-dashboard-spec.md
└── crm/
├── community-strategy.md
├── channel-architecture.md
├── new-member-journey.md
├── community-ritual-calendar.md
├── ambassador-program-brief.md
└── community-health-audit.md
Generated by Revenue Manager Source: marketingskills (revops v1.1.0, community-marketing v1.0.0)