opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/free-tool-strategy/references/detailed-guide.md

@@ -0,0 +1,550 @@
+# Free Tool Strategy (Engineering as Marketing) - Detailed Guide
+
+> This file contains the detailed procedure and reference material extracted from `SKILL.md` for focused loading. The root skill defines activation, examples, safety constraints, and limitations.
+
+## Initial Assessment
+
+Before designing a tool strategy, understand:
+
+1. **Business Context**
+   - What's the core product/service?
+   - Who is the target audience?
+   - What problems do they have?
+
+2. **Goals**
+   - Lead generation primary goal?
+   - SEO/traffic acquisition?
+   - Brand awareness?
+   - Product education?
+
+3. **Resources**
+   - Technical capacity to build?
+   - Ongoing maintenance bandwidth?
+   - Budget for promotion?
+
+---
+
+
+## Core Principles
+
+### 1. Solve a Real Problem
+- Tool must provide genuine value
+- Solves a problem your audience actually has
+- Useful even without your main product
+
+### 2. Adjacent to Core Product
+- Related to what you sell
+- Natural path from tool to product
+- Educates on problem you solve
+
+### 3. Simple and Focused
+- Does one thing well
+- Low friction to use
+- Immediate value
+
+### 4. Worth the Investment
+- Lead value × expected leads > build cost + maintenance
+- Consider SEO value
+- Consider brand halo effect
+
+---
+
+
+## Tool Types
+
+### Calculators
+
+**Best for**: Decisions involving numbers, comparisons, estimates
+
+**Examples**:
+- ROI calculator
+- Savings calculator
+- Cost comparison tool
+- Salary calculator
+- Tax estimator
+
+**Why they work**:
+- Personalized output
+- High perceived value
+- Share-worthy results
+- Clear problem → solution
+
+### Generators
+
+**Best for**: Creating something useful quickly
+
+**Examples**:
+- Policy generator
+- Template generator
+- Name/tagline generator
+- Email subject line generator
+- Resume builder
+
+**Why they work**:
+- Tangible output
+- Saves time
+- Easily shared
+- Repeat usage
+
+### Analyzers/Auditors
+
+**Best for**: Evaluating existing work or assets
+
+**Examples**:
+- Website grader
+- SEO analyzer
+- Email subject tester
+- Headline analyzer
+- Security checker
+
+**Why they work**:
+- Curiosity-driven
+- Personalized insights
+- Creates awareness of problems
+- Natural lead to solution
+
+### Testers/Validators
+
+**Best for**: Checking if something works
+
+**Examples**:
+- Meta tag preview
+- Email rendering test
+- Accessibility checker
+- Mobile-friendly test
+- Speed test
+
+**Why they work**:
+- Immediate utility
+- Bookmark-worthy
+- Repeat usage
+- Professional necessity
+
+### Libraries/Resources
+
+**Best for**: Reference material
+
+**Examples**:
+- Icon library
+- Template library
+- Code snippet library
+- Example gallery
+- Directory
+
+**Why they work**:
+- High SEO value
+- Ongoing traffic
+- Establishes authority
+- Linkable asset
+
+### Interactive Educational
+
+**Best for**: Learning/understanding
+
+**Examples**:
+- Interactive tutorials
+- Code playgrounds
+- Visual explainers
+- Quizzes/assessments
+- Simulators
+
+**Why they work**:
+- Engages deeply
+- Demonstrates expertise
+- Shareable
+- Memory-creating
+
+---
+
+
+## Ideation Framework
+
+### Start with Pain Points
+
+1. **What problems does your audience Google?**
+   - Search query research
+   - Common questions
+   - "How to" searches
+
+2. **What manual processes are tedious?**
+   - Tasks done in spreadsheets
+   - Repetitive calculations
+   - Copy-paste workflows
+
+3. **What do they need before buying your product?**
+   - Assessments of current state
+   - Planning/scoping
+   - Comparisons
+
+4. **What information do they wish they had?**
+   - Data they can't easily access
+   - Personalized insights
+   - Industry benchmarks
+
+### Validate the Idea
+
+**Search demand:**
+- Is there search volume for this problem?
+- What keywords would rank?
+- How competitive?
+
+**Uniqueness:**
+- What exists already?
+- How can you be 10x better or different?
+- What's your unique angle?
+
+**Lead quality:**
+- Does this problem-audience match buyers?
+- Will users be your target customers?
+- Is there a natural path to your product?
+
+**Build feasibility:**
+- How complex to build?
+- Can you scope an MVP?
+- Ongoing maintenance burden?
+
+---
+
+
+## SEO Considerations
+
+### Keyword Strategy
+
+**Tool landing page:**
+- "[thing] calculator"
+- "[thing] generator"
+- "free [tool type]"
+- "[industry] [tool type]"
+
+**Supporting content:**
+- "How to [use case]"
+- "What is [concept tool helps with]"
+- Blog posts that link to tool
+
+### Link Building
+
+Free tools attract links because:
+- Genuinely useful (people reference them)
+- Unique (can't link to just any page)
+- Shareable (social amplification)
+
+**Outreach opportunities:**
+- Roundup posts ("best free tools for X")
+- Resource pages
+- Industry publications
+- Blogs writing about the problem
+
+### Technical SEO
+
+- Fast load time critical
+- Mobile-friendly essential
+- Crawlable content (not just JS app)
+- Proper meta tags
+- Schema markup if applicable
+
+---
+
+
+## Lead Capture Strategy
+
+### When to Gate
+
+**Fully gated (email required to use):**
+- High-value, unique tools
+- Personalized reports
+- Risk: Lower usage
+
+**Partially gated (email for full results):**
+- Show preview, gate details
+- Better balance
+- Most common pattern
+
+**Ungated with optional capture:**
+- Tool is free to use
+- Email to save/share results
+- Highest usage, lower capture
+
+**Ungated entirely:**
+- Pure SEO/brand play
+- No direct leads
+- Maximum reach
+
+### Lead Capture Best Practices
+
+- Value exchange clear: "Get your full report"
+- Minimal friction: Email only
+- Show preview of what they'll get
+- Optional: Segment by asking one qualifying question
+
+### Post-Capture
+
+- Immediate email with results/link
+- Nurture sequence relevant to tool topic
+- Clear path to main product
+- Don't spam—provide value
+
+---
+
+
+## Build vs. Buy vs. Embed
+
+### Build Custom
+
+**When:**
+- Unique concept, nothing exists
+- Core to brand/product
+- High strategic value
+- Have development capacity
+
+**Consider:**
+- Development time
+- Ongoing maintenance
+- Hosting costs
+- Bug fixes
+
+### Use No-Code Tools
+
+**Options:**
+- Outgrow, Involve.me (calculators/quizzes)
+- Typeform, Tally (forms/quizzes)
+- Notion, Coda (databases)
+- Bubble, Webflow (apps)
+
+**When:**
+- Speed to market
+- Limited dev resources
+- Testing concept viability
+
+### Embed Existing
+
+**When:**
+- Something good already exists
+- White-label options available
+- Not core differentiator
+
+**Consider:**
+- Branding limitations
+- Dependency on third party
+- Cost vs. build
+
+---
+
+
+## MVP Scope
+
+### Minimum Viable Tool
+
+1. **Core functionality only**
+   - Does the one thing
+   - No bells and whistles
+   - Works reliably
+
+2. **Essential UX**
+   - Clear input
+   - Obvious output
+   - Mobile works
+
+3. **Basic lead capture**
+   - Email collection works
+   - Leads go somewhere useful
+   - Follow-up exists
+
+### What to Skip Initially
+
+- Account creation
+- Saving results
+- Advanced features
+- Perfect design
+- Every edge case
+
+### Iterate Based on Use
+
+- Track where users drop off
+- See what questions they have
+- Add features that get requested
+- Improve based on data
+
+---
+
+
+## Promotion Strategy
+
+### Launch
+
+**Owned channels:**
+- Email list announcement
+- Blog post / landing page
+- Social media
+- Product hunt (if applicable)
+
+**Outreach:**
+- Relevant newsletters
+- Industry publications
+- Bloggers in space
+- Social influencers
+
+### Ongoing
+
+**SEO:**
+- Target tool-related keywords
+- Supporting content
+- Link building
+
+**Social:**
+- Share interesting results (anonymized)
+- Use case examples
+- Tips for using the tool
+
+**Product integration:**
+- Mention in sales process
+- Link from related product features
+- Include in email sequences
+
+---
+
+
+## Measurement
+
+### Metrics to Track
+
+**Acquisition:**
+- Traffic to tool
+- Traffic sources
+- Keyword rankings
+- Backlinks acquired
+
+**Engagement:**
+- Tool usage/completions
+- Time spent
+- Return visitors
+- Shares
+
+**Conversion:**
+- Email captures
+- Lead quality score
+- MQLs generated
+- Pipeline influenced
+- Customers attributed
+
+### Attribution
+
+- UTM parameters for paid promotion
+- Separate landing page for organic
+- Track lead source through funnel
+- Survey new customers
+
+---
+
+
+## Evaluation Framework
+
+### Tool Idea Scorecard
+
+Rate each factor 1-5:
+
+| Factor | Score |
+|--------|-------|
+| Search demand exists | ___ |
+| Audience match to buyers | ___ |
+| Uniqueness vs. existing tools | ___ |
+| Natural path to product | ___ |
+| Build feasibility | ___ |
+| Maintenance burden (inverse) | ___ |
+| Link-building potential | ___ |
+| Share-worthiness | ___ |
+
+**25+**: Strong candidate
+**15-24**: Promising, needs refinement
+**<15**: Reconsider or scope differently
+
+### ROI Projection
+
+```
+Estimated monthly leads: [X]
+Lead-to-customer rate: [Y%]
+Average customer value: [$Z]
+
+Monthly value: X × Y% × $Z = $___
+
+Build cost: $___
+Monthly maintenance: $___
+
+Payback period: Build cost / (Monthly value - Monthly maintenance)
+```
+
+---
+
+
+## Output Format
+
+### Tool Strategy Document
+
+```
+# Free Tool Strategy: [Tool Name]
+
+## Concept
+[What it does in one paragraph]
+
+## Target Audience
+[Who uses it, what problem it solves]
+
+## Lead Generation Fit
+[How this connects to your product/sales]
+
+## SEO Opportunity
+- Target keywords: [list]
+- Search volume: [estimate]
+- Competition: [assessment]
+
+## Build Approach
+- Custom / No-code / Embed
+- MVP scope: [core features]
+- Estimated effort: [time/cost]
+
+## Lead Capture Strategy
+- Gating approach: [Full/Partial/Ungated]
+- Capture mechanism: [description]
+- Follow-up sequence: [outline]
+
+## Success Metrics
+- [Metric 1]: [Target]
+- [Metric 2]: [Target]
+
+## Promotion Plan
+- Launch: [channels]
+- Ongoing: [strategy]
+
+## Timeline
+- Phase 1: [scope] - [timeframe]
+- Phase 2: [scope] - [timeframe]
+```
+
+### Implementation Spec
+If moving forward with build
+
+### Promotion Plan
+Detailed launch and ongoing strategy
+
+---
+
+
+## Questions to Ask
+
+If you need more context:
+1. What's your core product/service?
+2. What problems does your audience commonly face?
+3. What existing tools do they use for workarounds?
+4. How do you currently generate leads?
+5. What technical resources are available?
+6. What's the timeline and budget?
+
+---
+
+
+## Related Skills
+
+- **page-cro**: For optimizing the tool's landing page
+- **seo-audit**: For SEO-optimizing the tool
+- **analytics-tracking**: For measuring tool usage
+- **email-sequence**: For nurturing leads from the tool
+- **programmatic-seo**: For building tool-based pages at scale

package/bundled-skills/freshdesk-automation/SKILL.md

@@ -221,6 +221,12 @@ Freshdesk uses page-based pagination:
 ## When to Use
 This skill is applicable to execute the workflow or actions described in the overview.
 
+## Example
+
+**User request:**
+
+> Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio).
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/frontend-architecture/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-architecture
-description: A portable, framework-agnostic architecture style for any React or React Native frontend. Organizes apps into feature modules with page/screen directories, a strict server-state vs UI-state split, barrel-only cross-module imports, co-located styles, and clear component-promotion rules....
+description: "A portable, framework-agnostic architecture style for any React or React Native frontend. Organizes apps into feature modules with page/screen directories, a strict server-state vs UI-state split, barrel-only cross-module imports, co-located styles, and clear component-promotion rules."
 risk: critical
 source: https://github.com/stareezy-1/frontend-architecture-skill/tree/main/skills/frontend-architecture
 source_repo: stareezy-1/frontend-architecture-skill

package/bundled-skills/frontend-data-contracts/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: frontend-data-contracts
-description: A portable, framework-agnostic discipline for type safety at the network edge of any React or React Native app. Establishes one typed API client as the single fetch boundary, a parse-don't-validate rule that turns wire JSON into trusted domain types before it enters the app, a single...
+description: "A portable, framework-agnostic discipline for type safety at the network edge of any React or React Native app."
 risk: critical
 source: https://github.com/stareezy-1/frontend-architecture-skill/tree/main/skills/frontend-data-contracts
 source_repo: stareezy-1/frontend-architecture-skill