proprietary-data-generator
Create original surveys, benchmarks, and aggregated data nobody else has. Automate data collection for content moats. Triggers on: "create original data", "proprietary data", "survey design", "benchmark study", "original research", "data-driven content", "create a survey", "industry benchmark", "aggregated data", "unique data", "first-party data", "data moat", "generate research data", "create a study", "original statistics", "data nobody else has", "competitive data advantage".
What this skill does
# Proprietary Data Generator
Create original surveys, benchmarks, and aggregated data that nobody else has. Proprietary data is the ultimate content moat — competitors can copy your writing style but they can't copy YOUR data. Automates the design and execution framework for data collection that feeds unique content angles.
## Stage
S7: Automation & Scale — Generating data at scale requires automation. This skill designs the collection system, not just one data point. Creates repeatable data assets that compound over time.
## When to Use
- User wants to create content that can't be replicated by competitors
- User asks about "original research", "surveys", "benchmarks", "proprietary data"
- User says "data moat", "unique data", "first-party data", "original statistics"
- After `content-moat-calculator` identifies the need for differentiated content
- User wants to build authority through data-driven content
- User wants to create linkable assets that earn backlinks naturally
## Input Schema
```yaml
niche: string # REQUIRED — topic area for data collection
# e.g., "AI video tools", "affiliate marketing"
data_type: string # OPTIONAL — "survey" | "benchmark" | "aggregation" | "case_study"
# Default: recommend based on niche and resources
audience_access: string # OPTIONAL — how you can reach respondents
# e.g., "email list of 500", "Reddit community", "Twitter followers"
# Default: suggest options
budget: string # OPTIONAL — "zero" | "low" ($0-100) | "medium" ($100-500) | "high" ($500+)
# Default: "zero"
goal: string # OPTIONAL — "content_moat" | "backlink_magnet" | "authority" | "lead_gen"
# Default: "content_moat"
```
**Chaining from S3 content-moat-calculator**: Use `competitive_advantages` to identify data moat opportunities.
## Workflow
### Step 1: Identify Data Opportunity
Analyze the niche for data gaps:
1. `web_search`: `"[niche] statistics 2025" OR "[niche] survey" OR "[niche] benchmark"` — what data already exists?
2. Identify gaps: what questions does the industry ask that nobody has answered with data?
3. `web_search`: `"[niche] reddit" "I wish I knew" OR "does anyone know"` — find unmet data needs
### Step 2: Design Data Collection
Based on `data_type` (or recommend the best fit):
**Survey Design:**
- 8-12 questions (shorter = higher completion)
- Mix: 70% multiple choice, 20% scale (1-5), 10% open-ended
- One "surprising" question that will generate headline-worthy data
- Target sample size: 100+ for credibility
- Distribution plan: where and how to reach respondents
**Benchmark Study:**
- Define metrics to measure (3-5)
- Data sources: public data, API calls, manual collection
- Collection methodology: how often, what tools
- Comparison framework: how to present findings
**Data Aggregation:**
- Sources to aggregate from (public databases, APIs, web scraping targets)
- Aggregation logic: how to combine and normalize
- Update frequency: one-time or recurring
- Visualization plan
**Case Study Collection:**
- Template for collecting stories (5-7 structured questions)
- Outreach template for requesting case studies
- Anonymization rules
- Minimum viable sample: 10+ cases
### Step 3: Create Collection Assets
Produce ready-to-use assets:
1. **Survey questions** (if survey) — complete question list with answer options
2. **Collection template** — spreadsheet structure or form layout
3. **Outreach template** — email/message to recruit respondents
4. **Data analysis plan** — how to turn raw data into insights
5. **Content plan** — how to present findings (blog post, infographic, report)
### Step 4: Design Automation
Create a repeatable system:
- Schedule: when to collect data (monthly, quarterly, annually)
- Tools: recommended platforms (Google Forms, Typeform, Airtable)
- Automation: how to automate collection and reporting
- Update process: how to refresh and republish with new data
### Step 5: Self-Validation
- [ ] Data gap is real (verified by search — nobody else has this data)
- [ ] Sample size is realistic given audience access
- [ ] Questions are unbiased and well-structured
- [ ] Collection method is feasible with stated budget
- [ ] Output content plan is specific (not just "write a blog post")
- [ ] Data is ethically collected (no scraping private data, survey has consent)
## Output Schema
```yaml
output_schema_version: "1.0.0"
proprietary_data:
niche: string
data_type: string
data_gap: string # What data doesn't exist yet
headline_potential: string # The "surprising finding" angle
collection:
method: string
sample_target: number
tools: string[]
timeline: string
budget_needed: string
assets:
survey_questions: object[] # If survey type
collection_template: string # Template description
outreach_template: string # Recruitment message
analysis_plan: string
content_outputs: # Content to create from the data
- type: string # "blog" | "infographic" | "report" | "social"
title: string
skill_to_use: string # Which skill creates this content
data_assets: string[] # Moat strengtheners for chaining
chain_metadata:
skill_slug: "proprietary-data-generator"
stage: "automation"
timestamp: string
suggested_next:
- "affiliate-blog-builder"
- "content-pillar-atomizer"
- "content-moat-calculator"
```
## Output Format
```
## Proprietary Data Plan: [Niche]
### The Data Gap
**Nobody has answered:** [the question]
**Why it matters:** [why people care]
**Headline potential:** "[Surprising finding template]"
### Collection Design
**Type:** [Survey / Benchmark / Aggregation / Case Study]
**Target sample:** XX responses
**Timeline:** X weeks
**Budget:** $XX
**Tools:** [tools list]
### Survey Questions (or Collection Template)
1. [Question] — [answer type] — [why this question]
2. [Question] — [answer type] — [why this question]
...
### Outreach Template
Subject: [subject line]
[email/message body]
### Content Plan (what to publish from this data)
1. **Blog post:** "[Title]" → build with `affiliate-blog-builder`
2. **Social thread:** Key findings → atomize with `content-pillar-atomizer`
3. **Lead magnet:** Full report PDF → distribute with `squeeze-page-builder`
### Automation Schedule
- **Collection:** [frequency]
- **Analysis:** [when after collection]
- **Publication:** [when after analysis]
- **Update:** [when to re-run with fresh data]
```
## Error Handling
- **No niche provided**: "Tell me your niche and I'll find data gaps nobody else is filling."
- **No audience access**: Suggest free distribution channels: Reddit, Twitter, niche forums, ProductHunt. "You don't need an email list — Reddit alone can drive 100+ survey responses."
- **Zero budget**: Design everything with free tools (Google Forms, Google Sheets, manual aggregation). "The best proprietary data costs $0 — just your time and curiosity."
- **Niche already well-researched**: Dig deeper. "The broad stats exist, but nobody has [specific angle]. Let's own that."
## Examples
**Example 1:** "I want original data about AI video tools"
→ Design survey: "AI Video Tools Usage Survey 2025" — 10 questions about which tools, satisfaction, spend, use cases. Distribute on Reddit r/aivideo, Twitter, LinkedIn. Target 150 responses. Content plan: "State of AI Video 2025" blog post + infographic.
**Example 2:** "Create a benchmark for affiliate marketing earnings"
→ Aggregate public data from case studies, combine with original survey. Monthly recurring data collection. "Affiliate Marketing Earnings Benchmark Q1 2025."
**Example 3:** "Data moat for my content strategy" (after content-moat-calculator)
→ Identify that competitors have generic content but NO original data. Design case Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.