Skip to content

Add Quarterdeck plugins (quarterdeck-goals, quarterdeck-guard) - #1653

Open
shannonbay wants to merge 2 commits into
davila7:mainfrom
shannonbay:add-quarterdeck
Open

shannonbay wants to merge 2 commits into
davila7:mainfrom
shannonbay:add-quarterdeck

Conversation

@shannonbay

@shannonbay shannonbay commented Nov 21, 2026 •

Copy link
Copy Markdown

What this PR does

Adds Quarterdeck to the aitmpl marketplace as two external plugins. Each catalog folder holds only source.json, pinned to commit 097c135 (the release branch at v0.31.0) of shannonbay/Quarterdeck (Apache-2.0).

  • plugins/productivity/quarterdeck-goals: path plugins/quarterdeck-goals, the plugin people install.
  • plugins/productivity/quarterdeck-guard: path plugins/quarterdeck-guard. quarterdeck-goals lists it in dependencies, so it has to be in the same marketplace for the install to resolve.

The pin is the release branch, not main, because only release carries the bundled MCP server (plugins/quarterdeck-goals/server/).

Quarterdeck runs standing goals for Claude Code, like "sell my birdcage on Facebook Marketplace" or "find the best new job ads each week". Each goal runs on a schedule in a background subagent, asks before it acts, and remembers what was decided. You approve or reject its proposals from a Goals pane beside the chat.

Type

  • New component
  • Change to an existing component
  • CLI (cli-tool/src, cli-tool/bin)
  • Website (dashboard/)
  • Docs or other

Checklist for components

  • Files are under cli-tool/components/{type}/{category}/ with a kebab-case name (plugins/productivity/quarterdeck-goals and quarterdeck-guard, matching each plugin's name)
  • Frontmatter has name and a specific description (in each .claude-plugin/plugin.json upstream)
  • No API keys, tokens or absolute paths; secrets are read from environment variables
  • If it runs code (hook script, MCP, mod), the README or description says what it runs and what it accesses (plugin READMEs and PRIVACY.md)
  • I did not commit docs/components.json or dashboard/public/ (they are regenerated after merge)

What it runs and accesses

  • MCP server (quarterdeck-goals, started from the plugin's .mcp.json; Node 22.13+ with built-in node:sqlite, no native build): keeps goals, run history, proposals and memory in one local SQLite file in the user's home folder (path overridable with QUARTERDECK_DB).
  • Hooks modules (both plugins): quarterdeck-goals starts due goal runs in background subagents and shows the Goals pane; quarterdeck-guard checks a goal run's tool calls against the autonomy the person set (refusing turned-off kinds of action, holding the rest for approval) and keeps run reports out of the chat.
  • Network: an update check at most every 6 hours that downloads the released plugin.json from raw.githubusercontent.com/shannonbay/Quarterdeck (off with QUARTERDECK_UPDATE_CHECK=0), and one-click unsubscribe requests (RFC 8058) only for unsubscribes the person allowed. Nothing about the user or their goals is sent anywhere. Details in PRIVACY.md.

How I tested it

Before tagging a release, Quarterdeck's release script runs claude plugin test on both plugins plus the unit tests and the live tests of the bundled server over stdio; this commit passed them. Both plugins install from it with claude plugin marketplace add shannonbay/Quarterdeck#release and claude plugin install quarterdeck-goals@quarterdeck.

🤖 Generated with Claude Code


Summary by cubic

Adds two Quarterdeck plugins to the marketplace under cli-tool/components/plugins/productivity/ so users can run standing goals and have a guard that enforces the autonomy they set.

  • New components: quarterdeck-goals (the installable plugin) and quarterdeck-guard (listed as its dependency, so it must live in the same marketplace to resolve), both pinned to shannonbay/Quarterdeck v0.31.0 via commit 097c135.
  • Pinned to the release branch rather than main because only release carries quarterdeck-goals' bundled MCP server.
  • Only source.json is added per component; the catalog (docs/components.json) must be regenerated after merge.
  • No required secrets or environment variables; optional overrides are QUARTERDECK_DB (SQLite file path) and QUARTERDECK_UPDATE_CHECK=0 (disable the update check).

Written for commit 8c83f99. Summary will update on new commits.

View guided diff

@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label Nov 21, 2026
@github-actions

Copy link
Copy Markdown
Contributor

👋 Thanks for contributing, @shannonbay!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. ✅ Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

⚠️ Do not commit generated catalog files

Please make sure your PR does not include docs/components.json or anything under dashboard/public/
(components.json, counts.json, search-index.json, components/*.json, component-content/**, api/v1/**).
Those files are regenerated automatically by scripts/generate_components_json.py after merge, and committing them causes merge conflicts.
If you already ran the script, revert them with: git checkout origin/main -- docs/components.json dashboard/public/

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

@greptile-apps

greptile-apps Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The metadata additions appear safe to merge.

Summary

Adds quarterdeck-goals and quarterdeck-guard as external plugins under productivity.

  • Quarterdeck goals and guard plugins appear in the aitmpl marketplace.

Reviews (1) · Last reviewed commit: "Add quarterdeck-guard plugin (pinned to ..." · Reviewed by Greptile

@shannonbay

Copy link
Copy Markdown
Author

About the SkillSpector failure: I went through the 23 findings on quarterdeck-goals (score 100, so it blocks as a new component). Nearly all are in the bundled server (server/*.mjs) and hooks bundle, and none of them is the behaviour the rule looks for:

Finding What's at the flagged line
P2 Hidden Instructions (cli 4980, mcp 24725) A byte-order mark in .replace(/^/, ""), stripping a BOM when reading state files
PE3 Credential Access .env, PE2 sudo (cli 4992-4994) sessionEnv() copying process.env (to drop CLAUDE_CODE_* vars before starting a session), and an error message suggesting sudo apt install tmux
AS1 ~/.claude/settings.json (README, hooks, cli 5375) The setup check (doctor) reporting when that file isn't valid JSON; the README explains the optional allow rules
YR4 tool poisoning, P6 prompt extraction, EA1 "use any tools", MP2 Bundled third-party code: ajv's validator codegen and the MCP SDK's toolChoice schema docs, plus long ?, ?, ? SQL placeholder lists
MP3 Memory Manipulation The remember tool's example text ("Never archive mail from the bank"), and the guard README listing what goal runs can't do ("can't … delete memory")
EA2 / RA2 autonomy and persistence Docs text ("without asking") and the README's description of the optional standing session (a systemd user timer on Linux, installed only by an explicit runner install)

What the plugin actually runs and accesses is listed under "What it runs and accesses" in the PR description and in PRIVACY.md. Happy to change anything you'd like before merging.

davila7 commented Nov 21, 2026

Copy link
Copy Markdown
Owner

Thanks for the contribution! This one goes to a maintainer's own review instead of the standard checks: both plugins ship hooks (hooks/hooks.json), and plugins with hooks always get a maintainer's review. No change is needed from you right now.


Generated by Claude Code

@davila7 davila7 added the triage:human Triage routine: needs Daniel's own review label Nov 21, 2026 — with Claude

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-pending Component PR awaiting maintainer review triage:human Triage routine: needs Daniel's own review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants