test-repo/skills/intelligent-article-research/SKILL.md

Intelligent Article Research

Download web articles, summarize them, AND extract actionable ideas specific to your projects.

Overview

This skill goes beyond basic summarization. It analyzes articles through the lens of YOUR current projects and goals, extracting:

• Implementation ideas
• Tools/libraries to try
• Pitfalls to avoid
• Opportunities for Mission Control / iOS apps / side hustle
• Action items with priority

Enhanced Workflow

Step 1: Extract & Summarize

Use Tavily to get full article content:

mcporter call tavily.tavily_extract 'urls=["URL_HERE"]' extract_depth=advanced

Step 2: Intelligent Analysis

Analyze the content against current context:

Your Active Projects:

• Mission Control (Phases 6-9 in progress, Phase 10+ planned)
• Gantt Board (maintenance mode)
• iOS Apps (6 apps, 2 live, 2 waiting LLC, 1 in review, 1 in progress)
• Daily Digest automation
• Blog Backup

Your Goals:

• Build iOS app empire
• Automate productivity
• Reduce manual work
• Scale side hustle

Your Tech Stack:

• OpenClaw, Next.js, Vercel, Supabase
• Swift, iOS, SwiftUI
• Tavily, mcporter

Step 3: Extract Actionable Ideas

For each article, identify:

1. Implementation Ideas (Specific to your stack)

• Features to add to Mission Control
• iOS app features to implement
• Automation opportunities
• Integration possibilities

2. Tools & Libraries

• New tools mentioned worth trying
• Alternatives to current tools
• Libraries that solve your problems
• SaaS services to evaluate

3. Patterns & Architectures

• Design patterns applicable to your projects
• Architecture decisions to consider
• Code organization ideas
• Database schema patterns

4. Pitfalls to Avoid

• Mistakes the author made (save you time)
• Anti-patterns in your context
• Things that don't scale
• Common failures in similar projects

5. Revenue/Business Opportunities

• Monetization strategies for your apps
• Side hustle ideas
• Market gaps identified
• Pricing strategies

6. Action Items

• Immediate actions (today/this week)
• Short-term (next 2 weeks)
• Long-term (Phase 10+ ideas)
• Research follow-ups

Step 4: Create Structured Document

Document Format:

# [Article Title]

**URL:** [url]  
**Source:** [domain] | [author]  
**Date Researched:** [YYYY-MM-DD]  
**Relevance Score:** [High/Medium/Low]  
**Tags:** [auto-generated + context-specific]

---

## Summary
[2-3 paragraphs]

## Key Insights for Your Context

### 1. Implementation Ideas for Mission Control
- [Specific feature idea with detail]
- [Architecture pattern to adopt]
- [UI/UX improvement]

### 2. iOS App Opportunities
- [Feature for existing apps]
- [New app idea inspired by article]
- [Technical approach to try]

### 3. Tools & Libraries to Explore
- **[Tool Name]** — [What it does] — [Why relevant]
- **[Library Name]** — [Use case] — [Integration effort]

### 4. Patterns Worth Adopting
- **[Pattern Name]** — [Description] — [Apply to: Mission Control/iOS/Both]
- **[Architecture]** — [Description] — [Benefits for your use case]

### 5. Pitfalls to Avoid (Learn from Author)
- [Mistake author made] → [How to avoid in your projects]
- [Anti-pattern identified] → [Better approach]

### 6. Business/Side Hustle Insights
- [Monetization idea]
- [Market opportunity]
- [Pricing strategy]

### 7. Content Ideas (for Daily Digest/Blog)
- [Topic to cover]
- [Angle to take]
- [Key points to emphasize]

## Action Items

### Immediate (This Week)
- [ ] [Specific action with context]
- [ ] [Quick win opportunity]

### Short-term (Next 2-4 Weeks)
- [ ] [Feature to implement]
- [ ] [Tool to evaluate]
- [ ] [Pattern to prototype]

### Long-term (Phase 10+ / Future)
- [ ] [Major architectural change]
- [ ] [Strategic shift to consider]
- [ ] [Big feature to plan]

### Research Queue
- [ ] [Follow-up article to read]
- [ ] [Tool documentation to review]
- [ ] [Competitor to analyze]

## Code Snippets & Examples

### [Useful code block 1]
```typescript
// From article, adapted to your context

[Useful code block 2]

// iOS implementation idea

Related to Your Current Work

Mission Control Phase X Connection

• [How this relates to current phase]
• [What to incorporate]

iOS App [Name] Connection

• [Specific app that could use this]
• [Implementation approach]

Gantt/Blog/Other Connection

• [Other project connections]

Questions to Explore

• [Question 1 inspired by article]?
• [Question 2 about implementation]?
• [Question 3 about viability]?

Final Recommendation

Priority: [High/Medium/Low]
Action: [Implement now / Research more / File for later / Skip]
Rationale: [Why this matters for your goals]

## Context-Specific Tagging

**Mission Control Relevance:**
- `#mission-control` — Directly applicable
- `#phase-6` through `#phase-13` — Which phase it supports
- `#automation` — Automation ideas
- `#agent-architecture` — Agent system patterns

**iOS Development Relevance:**
- `#ios` — iOS-specific
- `#swift` — Swift patterns
- `#swiftui` — UI ideas
- `#app-store` — Distribution/marketing
- `#coreml` — On-device ML

**Business/Side Hustle Relevance:**
- `#monetization` — Revenue ideas
- `#marketing` — Growth strategies
- `#indie-hacking` — Solo founder insights
- `#product-strategy` — Direction decisions

**Technical Relevance:**
- `#architecture` — System design
- `#performance` — Optimization
- `#security` — Safety considerations
- `#scaling` — Growth preparation

## Examples

### Example 1: Voxyz Article (Agent Architecture)

**Implementation Ideas Extracted:**
- Mission Control Phase 10: Daily Mission Generator using proposal → approve → execute loop
- Add Cap Gates to prevent task overload (max 3 urgent tasks/day)
- Reaction Matrix for smart suggestions (30% probability = human feel)

**Tools to Explore:**
- **OpenClaw roundtable** — For agent discussions (already have, use more)
- **Supabase policies** — For behavior configuration (adopt pattern)

**Pattern to Adopt:**
- **Single Proposal Service** — All mission creation through one function
- **Policy-driven config** — JSON in database, not hardcoded

**Pitfall to Avoid:**
- Don't run workers on both VPS and Vercel (race conditions)
- Don't skip auto-approve step when creating proposals

**Action Items:**
- [Immediate] Study Cap Gates implementation for Phase 10
- [Short-term] Design Proposal Service architecture
- [Long-term] Build Reaction Matrix for smart suggestions

### Example 2: iOS App Article (Revenue)

**Implementation Ideas:**
- Add subscription tiers to existing apps
- Implement paywall A/B testing
- Add referral program

**Tools to Explore:**
- **RevenueCat** — Subscription management (already using? evaluate)
- **Superwall** — Paywall optimization

**Pattern to Adopt:**
- **Freemium with clear upgrade path** — Current apps too generous?

**Business Insight:**
- Indie apps making $20k/mo use 3-tier pricing
- Free trial converts 40% better than no trial

**Action Items:**
- [Immediate] Audit current app pricing
- [Short-term] Implement trial for [App Name]
- [Long-term] Build 3-tier pricing model

## Automation Opportunities

**When reading articles, also extract:**

1. **Daily Digest Content**
   - Is this worth summarizing for the daily digest?
   - Angle for iOS devs? Entrepreneurs?
   - Key quote to feature?

2. **Task Creation**
   - Should this become a Gantt task?
   - Priority based on relevance?
   - Auto-assign to appropriate project?

3. **Tool Integration**
   - Does this suggest a new tool to add to TOOLS.md?
   - Worth a skill creation?
   - API worth exploring?

## Quality Checklist

Before marking research complete, verify:

- [ ] Summary captures main points
- [ ] At least 2 implementation ideas extracted
- [ ] Tools/libraries identified if mentioned
- [ ] Pitfalls noted (if author shared mistakes)
- [ ] Action items prioritized (immediate/short/long-term)
- [ ] Relevance to YOUR projects clear
- [ ] Not just "interesting" but "actionable"
- [ ] Code snippets captured if useful
- [ ] Questions for follow-up noted
- [ ] Final recommendation provided

## Success Metrics

**Good research isn't volume—it's action:**

- Did you implement an idea from the research?
- Did you avoid a pitfall the author warned about?
- Did you discover a tool that saved time?
- Did you create a task that moved a project forward?

**Bad research:**
- Interesting but no action taken
- Forgotten after reading
- No connection to current work

## Related Skills

- **tavily-web-research** — Basic extraction
- **url-research-documents** — Save to Mission Control
- Use together: This skill for analysis, others for extraction/storage