COMPLETE PLUGIN
View an example
Example installation for scribe
Example session using the verified commands above.
This skill should be used when managing Scribe projects from the CLI — creating, listing, renaming, deleting projects, linking projects to clients for invoicing, discovering project roots from the filesystem, assigning unassigned roots to project groups, linking git remotes to roots for automatic team project mapping, or viewing project details and statistics. Triggers include "create a project", "show my projects", "link project to client", "discover projects", "assign root", "set remote", "link git remote", "which project is this", "unassigned roots", "project management", or any mention of Scribe project groups, project roots, git remote mapping, or project-client associations.

Install the complete plugin to include its agents, hooks, commands, and runtime context.
Fastest path: hand this line to the coding agent doing the setup. It reads this page and installs the scribe plugin, which ships this skill with everything it relies on.
Click anywhere on the prompt to copy.
Choose a runtime, then follow its setup steps. This installs the complete scribe plugin.
COMPLETE PLUGIN
Example session using the verified commands above.
The portable SKILL.md on its own, without the plugin’s hooks, agents, commands, and companion skills. Use it only when you intentionally want the narrower path.
Pass the canonical page to a teammate or keep it close for later.
This skill should be used when the user asks for an activity report or work summary via Scribe — "generate a report", "report on my work", "what did the team get done", "billable vs internal time", "summary of last week/month", "exhaustive report", "PDF report for the client review", or any use of the generateReport capability (CLI `scribe report`, hub MCP, desktop MCP, hub chat, or the /reports page). Covers the three clarifying questions, the defaults, PDF/HTML export, and checking data freshness first.