avav25/marketing-operations
.claude/skills/marketing-operations/SKILL.md
Marketing operations knowledge base — MARKETING.md setup template, social media and email channel playbooks, trend research methodology, content calendar patterns, and recurring task definitions. Use when initializing marketing strategy, creating social media posts, drafting email campaigns, researching trends, or reviewing marketing analytics. Provides templates, platform-specific best practices, and quality checklists.
testing
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add avav25/ai-assets marketing-operationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 1:03 AM52.9s3 files scanned
SKILL.md
- name:
- marketing-operations
- description:
- Marketing operations knowledge base — MARKETING.md setup template, social media and email channel playbooks, trend research methodology, content calendar patterns, and recurring task definitions. Use when initializing marketing strategy, creating social media posts, drafting email campaigns, researching trends, or reviewing marketing analytics. Provides templates, platform-specific best practices, and quality checklists.
- user-invocable:
- true
Marketing Operations
Systematic marketing operations skill with strategy setup templates, channel-specific playbooks, and recurring task frameworks. Supports the /marketing workflow with reusable knowledge and templates.
When to Use
- Initializing marketing strategy for a project (MARKETING.md creation)
- Creating social media posts for X/Twitter, LinkedIn, Reddit
- Drafting email campaigns and newsletters
- Researching trends and content opportunities
- Planning community engagement
- Reviewing and adjusting marketing strategy
- Setting up a content calendar
When NOT to Use
- Writing blog posts (use
/blog-postworkflow withcontent-creationskill) - SEO audits (use
/seo-reviewworkflow) - Landing page design (use
/ui-ux-designworkflow) - Technical documentation (use
/docsworkflow)
Key Concepts
Marketing Strategy Hierarchy
Mission (why we exist)
└── Positioning (who we serve, what we offer, why us)
└── Messaging Framework (value prop, pillars, proof points)
└── Channel Strategy (where we show up)
└── Content Pillars (what we talk about)
└── Tactical Plan (what we do daily/weekly/monthly)
└── Content Calendar (specific tasks and dates)
Channel Selection Framework
Evaluate each channel on three dimensions before committing:
| Dimension | Question | |---|---| | Audience fit | Is our ICP active here? Can we reach them? | | Resource fit | Can we sustain the required publishing cadence? | | Content fit | Does our content type work on this platform? |
Rule: Better to do 2 channels well than 5 channels poorly. Start with 1-2 high-fit channels and expand only after consistent execution.
Content Pillar Model
Define 3-5 content pillars aligned with:
- ICP pain points — problems your audience actively searches for
- Product strengths — areas where your product genuinely excels
- Industry expertise — topics where you have unique knowledge or data
- Trending intersections — emerging topics that connect to your product
Each piece of content should map to exactly one pillar. Track pillar distribution to avoid over-indexing on one topic.
Measurement Framework
| Level | Metrics | Review Cadence | |---|---|---| | Vanity (awareness) | Impressions, followers, page views | Weekly (track, don't optimize for) | | Engagement | Likes, comments, shares, click-through rate | Weekly | | Pipeline | Signups, leads, demo requests, email subscribers | Weekly | | Revenue | Conversions, MRR impact, CAC, LTV | Monthly |
Rule: Optimize for pipeline and revenue metrics. Use vanity metrics only as leading indicators.
Resources
marketing-setup-template.md— Complete MARKETING.md template with all sections for strategy initializationchannel-playbooks.md— Platform-specific playbooks for X/Twitter, LinkedIn, Reddit, email, and community engagement
Integration
- Follows rules:
Agent(marketing-strategist)(strategy, positioning, demand gen),Agent(content-designer)(copywriting, social posts),Agent(content-writer)(blog, email content) - Used by workflows:
/marketing(primary),/blog-post(marketing context),/docs(public-facing content) - Companion skills:
content-creationskill (AI content tools, image generation, content briefs)
Related Skills
avav25/knowledge-sync
development
VerifiedTrustedCommunity
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
1SKILL.mdUpdated May 24, 2026
avav25/knowledge-sync-init
development
VerifiedTrustedCommunity
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
1SKILL.mdUpdated May 24, 2026
avav25/ai-skills-init
tools
VerifiedTrustedCommunity
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
1SKILL.mdUpdated May 18, 2026
avav25/plugin-author
tools
VerifiedTrustedCommunity
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.
1SKILL.mdUpdated May 14, 2026