Docsbook-io/docs-claude-plugins

COLLECTIONcommunity
v0.5.0Docsbook-ioUnknownUpdated 4mo agonpmGitHub

Claude Code plugin: /docs-sync pre-push workflow. Bundles 4 subagents, markdown-lsp MCP, and a git-hook installer

Claude Code plugins for documentation workflows — subagents, MCP servers, and git hooks bundled into one command. docs-sync • docs-create • docs-insights • How It Fits Together • Troubleshooting You push code. Your docs drift. Nobody notices until a user opens a GitHub issue saying "this doesn't match the README." Setting up the fix is painful: wire up subagents by hand, edit , write a pre-push…

This collection bundles
18 agents3 MCP servers16 commands

⚠ The trust score below reflects the installer package docs-claude-plugins only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
10Downloads/wk
4mo agoLast update
Package
AuthorDocsbook-io
LicenseUnknown
Version0.5.0
Sourcegithub
npmdocs-claude-plugins
GitHubDocsbook-io/docs-claude-plugins
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.5.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Claude Code plugins for documentation workflows — subagents, MCP servers, and git hooks bundled into one command. docs-sync • docs-create • docs-insights • How It Fits Together • Troubleshooting You push code. Your docs drift. Nobody notices until a user opens a GitHub issue saying "this doesn't match the README." Setting up the fix is painful: wire up subagents by hand, edit , write a pre-push hook script, figure out which model to pin where. Most teams skip it. Three plugins. One command…

Keywords
collection
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.