Borrowing it
Nothing to install: this file belongs to adeze/raindrop-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adeze/raindrop-mcp/master/.github/skills/raindrop-mcp-publishing/SKILL.mdgit clone --depth 1 https://github.com/adeze/raindrop-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/adeze/raindrop-mcp/raindrop-mcp-publishing)<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/raindrop-mcp-publishing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/raindrop-mcp-publishing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/adeze/raindrop-mcp/raindrop-mcp-publishing"><img src="https://agentmods.dev/badge/skills/adeze/raindrop-mcp/raindrop-mcp-publishing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 83 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 169 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- low Privilege Escalation · line 145 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01843 |
| Opus 5 | $0.00000 | $0.00922 |
| Sonnet 5 | $0.00000 | $0.00369 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
raindrop-mcp-publishing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Raindrop MCP Publishing Skill
Automates and manages the complete publishing workflow for @adeze/raindrop-mcp from version bumping through npm registry deployment.
Overview
This skill encapsulates the end-to-end publishing process, ensuring consistent version management, proper synchronization across configuration files, and reliable deployment via GitHub Actions with npm Trusted Publishers.
Publishing Workflow
1. Pre-Publication Checklist
Before publishing, verify:
- ✅ All tests passing:
bun run test - ✅ Type-check passing:
bun run type-check - ✅ Build successful:
bun run build - ✅ All changes committed to git
- ✅ No uncommitted work on master branch
2. Version Bump
Bump semantic version using Bun:
bun pm version <MAJOR.MINOR.PATCH>
Examples:
- Patch:
bun pm version 2.1.1(bug fixes) - Minor:
bun pm version 2.2.0(new features) - Major:
bun pm version 3.0.0(breaking changes)
3. Sync All Version Files
Update version numbers in ALL four files to maintain consistency:
Files to update:
- package.json - Already updated by
bun pm version - manifest.json - DXT manifest version (lines 2-4)
- CLAUDE.md - Project guidelines (around line 8)
- README.md - User documentation (around line 278)
Version reference locations:
// manifest.json
{
"dxt_version": "0.1",
"name": "@adeze/raindrop-mcp",
"version": "X.X.X",
// CLAUDE.md
### Version Information
- **Current version**: X.X.X
// README.md
## 📋 Recent Enhancements (vX.X.X)
4. Build & Commit
# Rebuild with new version
bun run build
# Stage all version updates
git add package.json manifest.json CLAUDE.md README.md
# Commit with semantic message
git commit -m "chore: bump version to X.X.X"
# Push to master
git push origin master
5. Create & Push Version Tag
# Create semantic version tag
git tag vX.X.X
# Push tag to trigger GitHub Actions
git push origin vX.X.X
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 289 lines · 0 tokens per session scan A 64187d77b311
raindrop-mcp-publishing is a skill published in the GitHub repository adeze/raindrop-mcp (184 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,843 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
pr-management
Manage the lifecycle of a GitHub PR - create, update the description, assign, refresh the branch and merge.