analyzer
Skill622 starsChanged 7 months agoMITView on GitHub
Content Analyzer — any content (URL, text, transcript) into structured analysis report with actionable insights. Use when user asks to analyze, summarize, or extract key takeaways from content.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- runesleo/x-readeredited, first seen Oct 26, 2026
- UtsavBalar1231/oh-my-claudeagenttheir own version, first seen Oct 13, 2026
- cline/skillstheir own version, first seen Jun 18, 2026
- cline/pluginstheir own version, first seen Jun 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- runesleo/x-reader★ 98895% same
Wrote their own version · 3
- cline/plugins★ 36same name
- cline/skills★ 35same name
- UtsavBalar1231/oh-my-claudeagent★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- feedgrab-batchSkill
- feedgrab-setupSkill
- feedgrabSkill
- videoSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
When user sends content (URL, text, or transcript) with analysis intent:
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Content Analyzer Skill
Any content → structured analysis report with actionable insights
Trigger
When user sends content (URL, text, or transcript) with analysis intent:
/analyze [URL]- "Analyze this article"
- "What are the key takeaways?"
- Auto-triggered after video/podcast transcription (from video skill)
Pipeline
Step 1: Get Content
Choose tool based on input type:
| Input | Tool |
| Tweet URL | fetch_tweet or Jina Reader |
| Web URL | WebFetch or Jina Reader |
| Local file | Read file directly |
| Transcript from video skill | Use directly |
Step 2: Multi-Dimensional Analysis
Scan content across these dimensions. Only output dimensions with actual content — skip empty ones.
## 📖 Summary
[1-3 sentence core thesis]
**Source**: [author/publisher] · [date]
**Type**: [tweet/article/video/podcast/report]
---
## 💡 Key Insights
### 🎯 Core Arguments
- **Thesis**: [Main argument or finding]
- **Evidence**: [Supporting data or reasoning]
- **Strength**: [How convincing? What's missing?]
### 🤖 Tools & Methods
- **What**: [Tools, frameworks, or techniques mentioned]
- **How**: [How they're used or applied]
- **Relevance**: [Could you use this?]
### ⚙️ Workflow Ideas
- **Optimization**: [Process improvements mentioned]
- **Automation**: [What could be automated]
- **Integration**: [How to fit into existing workflow]
### 📊 Data & Numbers
- **Key metrics**: [Important numbers mentioned]
- **Trends**: [Patterns in the data]
- **Gaps**: [What data is missing]
### ⚠️ Risks & Warnings
- **Pitfalls**: [Explicitly mentioned risks]
- **Blind spots**: [What the author might be missing]
- **Counter-arguments**: [Alternative perspectives]
### 🔗 Resources
- **Tools/APIs**: [Mentioned tools or data sources]
- **People**: [Worth following or referencing]
- **Further reading**: [Related content]
### 🧠 Mental Model Shifts
- **Before**: [Common assumption]
- **After**: [New understanding from this content]
- **Impact**: [How this changes decisions]
---
## ✅ Action Items
### Quick Wins (< 30 min)
- [ ] [Action 1] — Impact: ★★★★ | Effort: Easy
- [ ] [Action 2] — Impact: ★★★ | Effort: Easy
### Deeper Work (1-3 hours)
- [ ] [Action 3] — Impact: ★★★ | Effort: Medium
- [ ] [Action 4] — Impact: ★★ | Effort: Medium
### Exploration (needs validation)
- [ ] [Action 5] — Impact: ★★★ | Effort: Hard | Nature: ExploratoryStep 3: Personalized Relevance (Customizable)
Map insights to YOUR context. Edit the dimensions below to match your own projects, interests, and systems.
## 🔄 How This Applies to Me
### My Projects
- **[Project A]**: [How this insight connects]
- **[Project B]**: [What I could apply]
### My Knowledge Base
- **Update**: [Which notes/docs to update]
- **New entry**: [What to add to my knowledge system]
### My Decision Log
- **Changed my mind about**: [what and why]
- **Confirmed my belief that**: [what]Customization: Edit the dimensions in Step 2 and Step 3 to match your own domain. A trader might add "Market Impact" and "Risk Assessment". A developer might add "Architecture Patterns" and "Tech Debt". Make it yours.
Output Modes
| Mode | Trigger | Output |
| Full (default) | /analyze [URL] | All dimensions |
| Sparse | /analyze [URL] --sparse | Only hit dimensions, skip empty |
| Brief | /analyze [URL] --brief | Action items only |
Best Practices
- Scan all dimensions, but don't force-fill — skip empty dimensions cleanly
- Actions must be specific — not "learn about X" but "read X docs chapter Y"
- Distinguish fact from opinion — mark the author's claims vs verified facts
- Source everything — tag where each insight comes from in the original content
- ROI awareness — not every action is worth doing, assess effort vs impact
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

