claude-plugins
CLAUDE.md0 starsChanged 9 days agoMITView on GitHub
Public marketplace repo for the Devino Claude plugins. It holds only plugin manifests, icons, READMEs and skill text; every MCP server lives in its own app repo and this repo just points at the live MCP URL. The Claude plugin directory tracks main for each listed plugin and auto-publishes versions that pass its automated scan. There is no manual publish step in between. So: Owner ruling 2026-09-25. Never keep auto-publish on and skip the testing.
In this repository66 other files it gives its agents.
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- publishing-pagesSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
After the directory publishes the version, install it fresh from the directory and repeat the example prompts.
- Very specific: line 12
If the live proof cannot be done for a change, turn auto-publish off for that plugin on claude.ai/directory/manage before merging, and turn …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
claude-plugins
Public marketplace repo for the Devino Claude plugins. It holds only plugin manifests, icons, READMEs and skill text; every MCP server lives in its own app repo and this repo just points at the live MCP URL.
Every merge to main is a release
The Claude plugin directory tracks main for each listed plugin and auto-publishes versions that pass its automated scan. There is no manual publish step in between. So:
- A change to anything under
plugins/<name>/(manifest, skills, README, icon) is proven on the real client before it merges: install the plugin from this branch in Claude Code (or Cowork) as a user would, connect to the app's production MCP, run the listing's example prompts, and confirm the tool calls and the funnel events land in production. Write the proof with timestamps in the pull request. - After the directory publishes the version, install it fresh from the directory and repeat the example prompts. Log that too.
- A change to the app's served MCP surface (tools, annotations, OAuth, consent, host env) is a plugin change for this rule, even when this repo does not move.
- If the live proof cannot be done for a change, turn auto-publish off for that plugin on claude.ai/directory/manage before merging, and turn it back on once proven.
Owner ruling 2026-09-25. Never keep auto-publish on and skip the testing.
Checks
node scripts/sync-skills.mjs --check— the top-levelskills/mirror must matchplugins/*/skills/; regenerate with the same script without--check.claude plugin validate --strict .and per plugin folder. The strict validator rejects manifest keys it does not know (icon,privacyPolicyUrl); the directory picks up.claude-plugin/icon.pngand the README privacy link by itself.- Single-line commit subjects. No attribution trailers.
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.

