How do I install the Follow skill?

Run npx skillmds@latest add johnalbertini14-glitch/follow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Follow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Follow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Follow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Follow?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Follow by johnalbertini14-glitch — Agent Skill

Name: Follow
Rating: 4.666666666666667 (3 reviews)
Author: johnalbertini14-glitch

File contents

Workspace

~/follow/
├── sources/           # One file per followed entity
│   ├── people/        # @naval.md, @dhh.md
│   ├── topics/        # ai-safety.md, rust.md
│   └── feeds/         # techcrunch.md, hn-frontpage.md
├── archive/           # Captured content by date
│   └── YYYY-MM/
├── alerts.md          # Alert configuration
└── index.md           # Quick status: what's being followed

Quick Reference

Task	Load
Add/configure sources	`sources.md`
Set up filtering rules	`filtering.md`
Configure alert tiers	`alerts.md`
Query archived content	`querying.md`
Platform-specific setup	`platforms.md`

Core Loop

Add source: User names person/topic/feed → create tracking file
Monitor: Check sources on schedule (cron) or on-demand
Filter: Apply relevance rules, skip noise
Store: Archive what matters (summaries, not full dumps)
Alert: Notify based on tier (immediate/daily/weekly/passive)
Query: Answer "what did X say about Y?" from archive

Common Patterns

User says	Agent does
"Follow @naval on Twitter"	Create `sources/people/naval.md`, configure Twitter monitoring
"Track AI safety discussions"	Create topic tracker with keywords across multiple sources
"What has Competitor X posted this week?"	Query archive, synthesize summary
"Alert me immediately when Y happens"	Add to high-priority tier in `alerts.md`
"Give me a weekly digest of everything"	Configure weekly summary in alerts
"Stop following X"	Archive and mark inactive

Capture Principles

Summaries over full content — save space, stay legal
Links + timestamps always — retrievable later
Context for why it matters — not just "X posted"
Deduplicate across sources — same news from 5 places = 1 entry

---name: followdescription: Monitor content from people, topics, and sources across platforms with smart filtering, tiered alerts, and searchable archives.--- ## Workspace ``` ~/follow/ ├── sources/ # One file per followed entity │ ├── people/ # @naval.md, @dhh.md │ ├── topics/ # ai-safety.md, rust.md │ └── feeds/ # techcrunch.md, hn-frontpage.md ├── archive/ # Captured content by date │ └── YYYY-MM/ ├── alerts.md # Alert configuration └── index.md # Quick status: what's being followed ``` --- ## Quick Reference | Task | Load | |------|------| | Add/configure sources | `sources.md` | | Set up filtering rules | `filtering.md` | | Configure alert tiers | `alerts.md` | | Query archived content | `querying.md` | | Platform-specific setup | `platforms.md` | --- ## Core Loop 1. **Add source**: User names person/topic/feed → create tracking file 2. **Monitor**: Check sources on schedule (cron) or on-demand 3. **Filter**: Apply relevance rules, skip noise 4. **Store**: Archive what matters (summaries, not full dumps) 5. **Alert**: Notify based on tier (immediate/daily/weekly/passive) 6. **Query**: Answer "what did X say about Y?" from archive --- ## Common Patterns | User says | Agent does | |-----------|------------| | "Follow @naval on Twitter" | Create `sources/people/naval.md`, configure Twitter monitoring | | "Track AI safety discussions" | Create topic tracker with keywords across multiple sources | | "What has Competitor X posted this week?" | Query archive, synthesize summary | | "Alert me immediately when Y happens" | Add to high-priority tier in `alerts.md` | | "Give me a weekly digest of everything" | Configure weekly summary in alerts | | "Stop following X" | Archive and mark inactive | --- ## Capture Principles - **Summaries over full content** — save space, stay legal - **Links + timestamps always** — retrievable later - **Context for why it matters** — not just "X posted" - **Deduplicate across sources** — same news from 5 places = 1 entry

Frequently asked questions

Follow