Help us improve
Share bugs, ideas, or general feedback.
From finny
First-run initialization for the Finny plugin. Forces mandatory-read of core skills (finny-usage, intent-decomposer, judging-output), offers to enable the day_dream daily monitor, discloses the auto-approve hook, and writes a marker file. Idempotent — re-runs only on plugin version bump or explicit /finny:cowork-init invocation. Triggers: first time using finny tools, plugin onboarding, finny setup, plugin first run, finny install.
npx claudepluginhub postergully/finny-claude-plugin --plugin finnyHow this skill is triggered — by the user, by Claude, or both
Slash command
/finny:cowork-initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
First-run flow for the Finny plugin. Runs once per workspace; idempotent on
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
First-run flow for the Finny plugin. Runs once per workspace; idempotent on
re-runs (gated by a marker file at .claude/finny-plugin-initialized).
finny_* tool is about to be called,
AND the marker file is absent or stale, OR/finny:cowork-init.Before proceeding with any Finny tool call, you MUST read these three skills in order:
finny-usage — when to call Finny + which of the 4 public tools.intent-decomposer — discover→AskUser→execute orchestration. The load-bearing
one. Internalize the four iron rules.judging-output — envelope handling, intent-drift detection, error-code
branching, never-reformat rules.Do NOT call any finny_* tool until you've internalized all three.
AskUser:
"Do you want me to enable a daily 6 PM synthesis (
day_dream)? It runs while cowork is active, summarizes the day's interactions with Finny, and writes the synthesis back to Finny's memory for 11mirror writeback."
Three options:
monitors/monitors.json is
enabled. (It's enabled by default once the plugin loads — this is just
acknowledgment.)HH:MM in 24-hour format, then write
the user's choice into a session memory note for the day_dream skill to
honor at runtime. (The monitor itself fires daily at 18:00; if the user
wants a different time, day_dream skill skips when triggered outside the
user's preferred hour.)/finny:cowork-init again to revisit.Print:
"This plugin auto-approves these 5 Finny MCP tool calls (no per-call prompt):
finny_query,finny_report,finny_task_status,finny_continue,finny_remember. The bridge has its own destructive-intent guard. To revoke, disable the plugin in/plugin."
Write .claude/finny-plugin-initialized with this content:
{
"initialized_at": "<ISO-8601 timestamp>",
"plugin_version": "<from .claude-plugin/plugin.json>",
"day_dream_enabled": true,
"day_dream_hour": 18
}
Use the Write tool to create the marker file. Set day_dream_enabled: false
if user chose "No, skip for now". Set day_dream_hour to the user's chosen
hour if they picked custom.
After init has run (this session or a previous one), check: "did day_dream run
yesterday?" Look for a tag day_dream/<YYYY-MM-DD> in cowork's session memory
or by querying Finny briefly. If not, AskUser:
"Yesterday's day_dream didn't run. Want to run it now?"
If yes, invoke /finny:day_dream YYYY-MM-DD (the previous date).
If marker plugin_version < current plugin.json version, re-run the full init
flow. This lets us add new mandatory-read skills in 0.2.0+ without operator
action.
When re-running on version bump, SKIP the day_dream cron offer if the marker shows it was previously answered (yes or no). Don't re-ask choices the user already made.
All cowork-side. Marker lives in the user's .claude/ directory.
finny-usage, intent-decomposer, judging-output — the mandatory-read skills.day_dream — the skill the cron schedules.