docs
Skill17 starsChanged 3 days agoApache-2.0View on GitHub
The skill that gets installed into every detected agent by vs skill install lives at: skills/vibesurfer/SKILL.md That file is the single source of truth — it's what the agent reads, and it's the file vs skill install writes (verbatim) into each agent's conventional skill location: The same vs skill install call also writes an mcpServers.vibesurfer = {command: "vs", args: ["mcp"]} entry into each agent's MCP config (.claude.json, ~/.codex/config.toml, <workspace>/.cursor/mcp.json, ~/.gemini/settings.json, Library/Application Support/Claude/claude_desktop_config.json on macOS) so the agent can talk to…
169 other projects use a version of this.
Adopted by
Most recently taken up by
- RLinf/RLinftheir own version, first seen Nov 15, 2026
- cpoder/claude-apple-plugintheir own version, first seen Nov 15, 2026
- Canonry/agent-readinesstheir own version, first seen Nov 15, 2026
- automagik-si/genietheir own version, first seen Nov 15, 2026
- Adelie-Squad/solosquadtheir own version, first seen Nov 8, 2026
- hhtower/price-comparisontheir own version, first seen Nov 8, 2026
Used with
Projects with it also use import-memory, perf and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
amirbironSkillimport-memory
Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.
Also in 3 projects that use this
MicrosoftSkillperf
Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.
Also in 4 projects that use this
diego-tobalinaSkillbuild-fix
Fix build and compilation errors systematically. Run when build fails.
Also in 3 projects that use this
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 4 projects that use this
vbrevikSkillwork
Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.
Also in 7 projects that use this
mbwsimsSkillimpact
This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.
Also in 3 projects that use this
Other versions169 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 169
- remotion-dev/remotion★ 73ksame name
- PrefectHQ/fastmcp★ 29ksame name
- jlowin/fastmcp★ 29ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- micronaut-projects/micronaut-core★ 6.4ksame name
- RLinf/RLinf★ 5.7ksame name
- latitude-dev/latitude-llm★ 4.7ksame name
- samuelgursky/davinci-resolve-mcp★ 4.1ksame name
- TanStack/ai★ 3.4ksame name
159 more not listed
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 repository2 other files it gives its agents.
- debug-failed-actionSkill
- vibesurferSkill
The file
Files
Skill
The skill that gets installed into every detected agent by vs skill install lives at:
skills/vibesurfer/SKILL.md
That file is the single source of truth — it's what the agent reads, and it's the file vs skill install writes (verbatim) into each agent's conventional skill location:
| Agent | Path |
| Claude Code | ~/.claude/skills/vibesurfer/SKILL.md |
| Codex CLI | ~/.codex/skills/vibesurfer/SKILL.md |
| Cursor | <workspace>/.cursor/skills/vibesurfer/SKILL.md |
| Gemini | ~/.gemini/extensions/vibesurfer/GEMINI.md (renamed) |
| OpenClaw | ~/.openclaw/workspace/skills/vibesurfer/SKILL.md |
| Canonical | ~/.agents/skills/vibesurfer/SKILL.md |
The same vs skill install call also writes an mcpServers.vibesurfer = {command: "vs", args: ["mcp"]} entry into each agent's MCP config (.claude.json, ~/.codex/config.toml, <workspace>/.cursor/mcp.json, ~/.gemini/settings.json, Library/Application Support/Claude/claude_desktop_config.json on macOS) so the agent can talk to vibesurfer over MCP as well as via the SKILL.md.
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.

