Adds the `ciagent` external git-subdir plugin (testing category, Apache-2.0) pointing at suniel12/ciagent//plugins/ciagent — two skills (onboard, check) for pytest-native regression testing of the agent being built. Follows the qa-orchestra/storymap precedent (external entries live only in the Claude marketplace). Maintainer disclosure present. Counts reconciled to 92 plugins / 4 externals; make validate STRICT=1 clean. External repo verified public + valid plugin manifest.
Adds the source-native `hermes-tweet` plugin (Hermes Agent X/Twitter research + approval-gated action workflows) with Claude/Codex manifests and a portable skill. Registered across the Claude, Codex, and Cursor marketplaces; catalog counts updated to 91 plugins / 162 skills. Maintainer disclosure present per the #611 policy. Verified: make validate STRICT=1 clean across 5 harnesses, make garden 0 errors.
Recounted from the filesystem: 90 plugins (87 local + 3 external),
161 skills across 45 plugins. Also catches docs/usage.md and
docs/plugins.md install-note lines missed by earlier syncs.
Add Claude Fable 5 (model: fable) as the tier above opus across the
adapter framework - native passthrough in Claude Code, mapped to each
harness's top model elsewhere. No agents are promoted yet; tier criteria
and cost guidance are documented in docs/agents.md and docs/authoring.md.
Refresh MODEL_ALIASES against current harness catalogs (June 2026):
- Codex: gpt-5 family -> gpt-5.5 / gpt-5.4-mini (per Codex model docs)
- Copilot: GPT-5 stand-ins -> native Claude models (claude-opus-4.8,
claude-sonnet-4.6, claude-haiku-4.5) now that Copilot CLI serves them
- OpenCode: opus -> anthropic/claude-opus-4-8; haiku dated pin ->
latest-tracking anthropic/claude-haiku-4-5
- Gemini: intentionally stays on GA gemini-2.5-* (3.x is preview-gated)
- plugin-eval judge opus tier -> claude-opus-4-8
Gates: generate-all (no committed drift), validate STRICT=1, garden,
test (442 passed), smoke-test all green.
PR #558 updated the headline totals but left trailing references at
83/191/155 across README, AGENTS.md, GEMINI.md, ARCHITECTURE.md, and
docs/*. Sync them all to the true counts (82 local + 2 external = 84
plugins, 192 agents, 156 skills).
Also runs make generate-all to bring the committed harness registries in
sync — adds the social-publishing entries to .agents/ and .cursor-plugin/
(which the original PR could not regenerate) and fixes the stale count in
the generated cursor manifests.
Left round-trip-results.md (point-in-time CLI verification results) and
plugin-eval.md (grade threshold) unchanged.
Add lean, native plugin-install entry points so each harness's own plugin
manager can install this marketplace (mirroring obra/superpowers) — committing
only small JSON registries, not duplicated skill/agent content trees.
- Codex: committed marketplace registry (.agents/plugins/marketplace.json) +
per-plugin manifests (plugins/*/.codex-plugin/plugin.json). Entries point at
source ./plugins/<name>; Codex reads SKILL.md directly. Transformed
.codex/skills|agents stay gitignored.
- Cursor: commit the existing .cursor-plugin/ marketplace + .cursor/rules/
(these already point at source plugins/).
- Gemini: gemini-extension.json already committed (contextFileName: AGENTS.md);
transformed trees stay gitignored (install via clone + make generate).
- OpenCode: unchanged — install via `make install-opencode` (transformed tree
stays gitignored).
- CLAUDE.md is now a symlink to AGENTS.md; Claude-Code addenda moved to
docs/harnesses.md.
- CI: new step fails if `make generate-all` drifts from the committed registries.
Net new committed: ~720 KB of manifests (no skill/agent duplication). Adds
round-trip tests for the new registries + the symlink. Docs updated across
README, docs/harnesses.md, ARCHITECTURE.md, CONTRIBUTING.md, GEMINI.md,
docs/authoring.md, and the PR template.
- Add model: haiku to agent frontmatter (required by docs/authoring.md)
- Rename agent to social-publishing-publisher for plugin-scoped naming
- Remove non-standard license: field from SKILL.md frontmatter
- Update catalog counts and listings in AGENTS.md, README.md,
docs/plugins.md, docs/agents.md, docs/agent-skills.md
* feat(adapters): multi-harness framework + harness_portability eval dimension
Turn this Claude Code plugin marketplace into a generic agentic-harness
marketplace. Adapters under tools/adapters/ emit harness-native artifacts
for OpenAI Codex CLI, Cursor, OpenCode, and Gemini CLI from a single
Markdown source. Source-of-truth stays under plugins/ — Claude Code is
unchanged.
Framework (tools/adapters/):
- base.py — PluginSource parser, HarnessAdapter ABC, write/mirror helpers
(path-traversal guard, UTF-8-safe), inline-list + block-list + block-scalar
YAML-ish parser, _utf8_safe_cut, _split_inline_list, _normalize_author
- capabilities.py — per-harness capability matrix, TOOL_NAME_MAPS,
MODEL_ALIASES, resolve_model() with explicit warnings
- codex.py — emits .codex/{skills,agents}/ + AGENTS.md (≤150-line
table-of-contents). Fence-aware body splitter, _utf8_safe_cut for
multibyte safety, _yaml_scalar with reserved-word + special-char quoting.
Skill/command name collision detection (and second-order __cmd fallback).
- cursor.py — emits .cursor-plugin/{plugin,marketplace}.json + curated
.cursor/rules/*.mdc. _validate_mdc_frontmatter handles YAML block scalars
(no false positives on colons in description body). _normalize_author
handles dict, npm-style strings, and author lists.
- opencode.py — transpiles agents to .opencode/agents/<id>.md with
mode:subagent + permission: deny-everything-else block (skill/task always
allowed as base capabilities — Claude's implicit defaults).
- gemini.py — emits native skills/, agents/, and commands/ at extension
root (April 2026 spec). Tool-allowlist remapped via TOOL_NAME_MAPS.
CLI + tooling:
- tools/generate.py — unified `make generate HARNESS=<x> [PLUGIN=<y>]`,
with --clean (containment-guarded; case-insensitive on Darwin/Win32),
--prune (orphan removal across all per-harness output trees), --strict
(warnings fail), per-plugin error aggregation, refuses --clean --plugin
(would silently wipe other plugins' artifacts).
- tools/validate_generated.py — structural validation across all four
harness outputs. Codex 8KB cap → error. _extract_permission_block
correctly handles nested permission keys (column-0 only).
- tools/doc_gardener.py — recurring drift detection per OpenAI harness-
engineering principle. STALE_ARTIFACT (info), DEAD_LINK (error),
MARKETPLACE_ORPHAN (error), SKILL_OVER_CODEX_CAP (warning), grouped
output sorted by severity.
plugin-eval (extends existing framework):
- New harness_portability dimension (6% weight, rebalanced from existing
static sub-scores). Surfaces non-portable patterns with concrete
remediation hints: SKILL_OVER_CODEX_CAP, CLAUDE_TOOL_REFS,
CLAUDE_TOOL_PROSE, AGENT_NAME_COLLISION, BARE_MODEL_ALIAS.
- _CAMEL_TOOL_PATTERN requires Claude-tool context (no false positives
on Rust's `Task` etc.). _TOOL_PROSE_PATTERN case-sensitive on tool
names, case-insensitive on the leading article.
- Findings do NOT also feed anti_pattern_penalty (no double-counting).
Documentation:
- Top-level guides: CODEX.md, CURSOR.md, OPENCODE.md (≤150 lines each,
table-of-contents pattern per OpenAI harness-engineering post)
- docs/harnesses.md — capability matrix, graceful-degradation table,
generated output paths
- docs/authoring.md — portable-content style guide (tools, models,
collision rules, fence-respect)
- docs/round-trip-results.md — real-CLI verification recipes (OpenCode
discovers 193 subagents, Gemini extensions validate passes, Codex
TOMLs all parse)
- CONTRIBUTING.md — new file pointing at docs/authoring.md
- README.md — rewritten for multi-harness (145 lines, was 460)
- CLAUDE.md — trimmed to 60-line table-of-contents
- GEMINI.md — trimmed from 1500 to 500 tokens (3× over budget previously)
Tests: 181 passing (103 plugin-eval + 78 tools/tests). Real-CLI round-trip
verified for OpenCode, Gemini, and Codex (TOML parses).
Replaces tools/generate_gemini_commands.py with the unified CLI.
* refactor(skills): extract detail to references/details.md (~75 skills)
Apply Anthropic's canonical SKILL.md progressive-disclosure pattern across
the marketplace: SKILL.md body becomes a navigation tier (trigger phrasing
+ quick start), detailed templates and worked examples move to
references/details.md (loaded on demand by the agent).
Motivation: OpenAI Codex CLI hard-truncates skills at 8 KB. Before this
change, ~90 skills exceeded that cap and would silently break on Codex.
The progressive-disclosure pattern is also Anthropic's documented
recommendation for token efficiency — Claude Code reads references/ files
on demand when the body navigation says to.
What's extracted, by pattern:
- Pass 1 (## Templates section): 19 skills — full template libraries
moved to references/details.md
- Pass 2 (## Implementation Patterns / ## Advanced Patterns): 13 skills
- Pass 3 (everything between nav-tier and wrap-tier headings): 53 skills
- Conservative re-extraction for 8 skills that got over-reduced — kept
~6-7 KB inline (most of the quick-start tier) plus references/ overflow
What stays inline (SKILL.md navigation tier):
- description: frontmatter (triggering — unchanged for all skills)
- ## When to Use This Skill / ## Core Concepts / ## Quick Start
- ## Best Practices / ## Troubleshooting / ## See Also wrap-ups
- A pointer note ("see references/details.md") so the agent knows where
to look for detail
What goes to references/details.md (detail tier, on-demand load):
- ## Templates (full code template libraries)
- ## Implementation Patterns / ## Advanced Patterns (deep examples)
- Mid-skill walkthroughs that exceed the inline budget
Also in this commit:
- plugins/brand-landingpage description trimmed from 958→543 chars
(preserves trigger phrasing, drops verbose example-quote list)
Net effect:
- SKILL_OVER_CODEX_CAP findings: 90 → 10 (88% reduction)
- All triggers unchanged — discovery behavior identical across harnesses
- 75 new references/details.md files with the extracted content
- Same depth of guidance, loaded progressively
Remaining 10 oversized skills are complex multi-section docs (e.g.
postgresql, code-review-excellence, evaluation-methodology) that need
per-skill manual judgment — flagged by `make garden` for future work.
* chore: bump all plugin versions (multi-harness release)
Patch-bump every local plugin (81) in both .claude-plugin/marketplace.json
entries and each plugins/<name>/.claude-plugin/plugin.json. Minor-bump the
top-level marketplace metadata.version (1.6.0 → 1.7.0) to signal the
multi-harness adapter framework addition.
The external git-subdir entry (qa-orchestra) is unaffected — its version
is governed by its upstream repo.
* fix(opencode): preserve explicit tools:[] + word-boundary subtask match
Addresses two Codex review findings on PR #541.
## P1 — `tools: []` silently upgraded to permissive (privilege escalation)
Before: `_build_permission_block` returned `{}` for any empty list, which
omits the `permission:` block entirely from the emitted agent. An author
who explicitly wrote `tools: []` to lock down an advisory-only agent got
an UNRESTRICTED agent in OpenCode. Affected agent in this tree:
`plugins/arm-cortex-microcontrollers/agents/arm-cortex-expert.md`.
Fix: `_build_permission_block` now takes a `has_tools_field` flag so the
caller can distinguish "tools: key missing" (Claude default permissive)
from "tools: []" (explicit lock-down). The lock-down case emits a
deny-everything block that allows ONLY the base capabilities (skill, task)
that Claude Code always grants implicitly. Verified against the real
arm-cortex-expert agent — now emits read/edit/write/bash/grep/glob/list:
deny, task/skill: allow.
## P2 — `"agent" in cmd.body.lower()` false-positives on substrings
Before: a command body containing `PerformanceReviewAgent` (class name
in a code snippet) or `useragent` triggered `subtask: true`, changing
runtime behavior based on incidental text.
Fix: switch to a compiled word-boundary regex `\b(agent|subagent)s?\b`
(case-insensitive). Tests confirm the substring `PerformanceReviewAgent`
no longer fires, while a real "spawn a subagent" sentence still does.
## Tests
3 new regression tests in tools/tests/test_adapters.py:
- `test_explicit_empty_tools_yields_locked_permission_block` (P1)
- `test_missing_tools_field_yields_no_permission_block` (P1 boundary)
- `test_subtask_inference_word_boundary` (P2)
184 total tests pass (was 181). OpenCode round-trip still discovers all
193 subagents; arm-cortex-expert agent is now properly locked down.
* test: behavioral verification + CI gates for multi-harness pipeline
Adds three layers of automated verification that pure-Python parser tests
miss, plus the CI jobs that turn them into hard gates. Catches the kinds
of issues that previously only surfaced when a real user installed the
marketplace and tried to use it.
## test_real_world.py — real-source structural tests
Runs against the actual `plugins/` tree (not synthetic fixtures). Catches
issues that only appear on real content:
- every marketplace entry resolves to a plugins/<name>/ dir
- every local plugin dir appears in marketplace.json
- marketplace.json version == per-plugin plugin.json version (catches drift)
- every plugin loads via load_plugin() without error
- no plugin name contains `__` (adapter namespace separator)
- every agent has name + description; every skill has a trigger phrase
(same regex plugin_eval's MISSING_TRIGGER check uses)
- no agent name collides with Codex built-ins
- every refactored skill (with `references/details.md`) has:
- meaningful detail content (>=500 B in details.md)
- a pointer to references/ in the SKILL.md body
- a navigation-tier heading preserved (When to Use, Overview, etc.)
- body >= 600 B (not a stub)
- every plugin.json has name + version matching the dir
This test pass found and fixed three real defects before commit:
- ship-mate/skills/scan: description had no trigger phrase ("Use when…")
- reverse-engineering/skills/memory-forensics: nav-tier section lost
during extraction
- reverse-engineering/skills/binary-analysis-patterns: same
All three are now fixed (preserved trigger phrasing, added When-to-Use
sections back to the skills my extraction over-trimmed).
## test_round_trip.py — generate→parse→verify
CI runs this AFTER `make generate-all`. Catches generation-time regressions:
- OpenCode/Codex/Gemini agent counts match source agent count (no skips)
- every Codex SKILL.md under 8 KB (the cap that would silently truncate)
- every Codex agent TOML has required fields + valid sandbox_mode
- every OpenCode agent has mode in {primary,subagent,all} and
provider-prefixed model
- locked agents (source `tools: []`) emit proper deny-everything permission
block with skill/task allow (regression guard for PR-541 P1)
- every Gemini @{path} injection resolves to a real source file
- every Gemini command TOML has prompt + {{args}} placeholder
- every context file (CLAUDE.md, AGENTS.md, GEMINI.md, etc.) within
150-line cap
- Cursor marketplace + per-plugin manifests cover all local plugins
- .cursor/rules/*.mdc only use the 3 documented frontmatter keys
## test_cli_smoke.py — real-CLI subprocess tests
Invokes the actual harness binaries (OpenCode, Gemini, Codex, Claude Code)
against the generated artifacts. Catches CLI-level issues pure-Python
parsing can't see: schema-loader drift, plugin-discovery bugs, version
incompatibilities.
- `opencode agent list` — must succeed AND discover every source agent
(currently 191 + 2 OpenCode built-ins)
- `gemini extensions validate <repo>` — must return success
- `codex doctor` — must report healthy install
- every Codex agent TOML must parse with stdlib `tomllib`
- `claude --version` — sanity check the Claude Code CLI loads
- marketplace.json must have owner + metadata.version for Claude Code's loader
Per-CLI tests skip gracefully when the binary isn't on PATH, so local
devs only exercise what they have installed. CI installs OpenCode +
Gemini and turns those skips into hard gates.
## Makefile + CI
- `make test` — full pytest suite (plugin-eval + tools/tests/)
- `make smoke-test` — generates if needed, then runs real-CLI smoke tests
- `.github/workflows/validate.yml` extended with:
- `tools-tests` job — runs pytest tools/tests/
- `multi-harness-generate` job — `make generate-all && make validate
STRICT=1 && make garden`, uploads generated artifacts on every run
- `cli-smoke-test` job — installs OpenCode + Gemini, runs test_cli_smoke.py
## Test counts
- Before: 184 tests
- After: 386 tests (parameterized real-source tests over all 82 plugins)
- All passing locally on OpenCode 1.15.7 + Gemini 0.42.0 + Codex 0.133.0
+ Claude Code 2.1.148
* chore: add .worktrees/ to .gitignore
Isolate git worktrees from version control to keep repository clean.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: add Gemini CLI extension manifest
- Declare claude-agents as a Gemini CLI extension
- Point to GEMINI.md for bootstrap context
- Enable auto-discovery via gemini-cli-extension topic
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: add Gemini CLI bootstrap context
- Document 150+ skills ecosystem for Gemini users
- Explain differences from Claude Code platform
- Provide plugin navigation and skill usage guidance
- Link to tool mapping and plugin catalog
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs: Add Gemini CLI tool mapping reference
Add comprehensive docs/gemini-tool-mapping.md guide for users migrating from
Claude Code to Gemini CLI. Includes:
- Core Tools: Direct Equivalents (table format)
- Platform-Specific Features: Claude Code Only (slash commands, subagents, model tiers)
- Claude Code Specific: MCP Servers (description and migration guidance)
- Platform Differences: Behavior & Constraints (context limits, tool availability)
- Skill Design Guidelines (DO's and DON'Ts for Gemini compatibility)
- Migration Path (step-by-step guide for adapting Claude Code skills)
- Common Patterns (side-by-side code examples)
- FAQ (troubleshooting and common questions)
Document provides practical, self-contained guidance without requiring other docs,
though cross-references to GEMINI.md and plugins.md are included.
Co-authored-by: GitHub Copilot <noreply@github.com>
* fix: Correct syntax errors in code examples
- Lines 177-189: Convert Python pseudocode to valid bash for skill examples
- Line 347: Remove invalid read_file() function call; use sed for line extraction
- Lines 365-372: Replace mixed Python/bash with proper bash conditionals using exit codes
All code examples now syntactically valid and follow Gemini CLI bash patterns.
Co-authored-by: GitHub Copilot <copilot@github.com>
* docs: add Gemini CLI section to README
- Explain Gemini CLI extension availability and installation
- Link to GEMINI.md for navigation and tool mapping for platform differences
- Clarify multi-platform support (Claude Code primary, Gemini CLI skills)
* docs: add Gemini CLI plugin discovery guide
- List all 79 plugins organized by category with skill names
- Include natural-language trigger examples for Gemini auto-activation
- Complement GEMINI.md with detailed skill discovery navigation
* docs: update GEMINI.md to reference Gemini-optimized plugin guide
- Point plugin catalog navigation to gemini-plugin-guide.md for Gemini users
- Keep reference to plugins.md as full technical catalog fallback
* fix: remove trailing period from reference in GEMINI.md
* fix: correct repo URL, extension version, gitignore, and doc references
- Point install URL to upstream wshobson/agents (not fork)
- Set extension version to 1.0.0 (initial release)
- Fix .gitignore: restore .claude entry, add .worktrees/
- Fix broken @./plugins.md references → @./docs/plugins.md in tool-mapping doc
* fix: align Gemini extension name with marketplace, fix @./ refs, deduplicate plugin listing, fix pseudo-code, update README plugin count
* docs: add per-plugin GEMINI.md for all 79 plugins + generation script
Generated programmatically from each plugin's agents/commands/skills
frontmatter. Covers all three component types per plugin, providing
scoped context for Gemini CLI slash commands and developer workflows
inside the repo tree.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: add ADR for Gemini CLI integration strategy
Documents the four options considered, why hierarchical GEMINI.md
scanning and per-repo splitting were rejected, and the key findings
(slash commands are supported in Gemini; install granularity is a
hard platform limit). Records pending Phase A work.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat: add Gemini CLI slash commands for all 100 plugin commands
Creates commands/<plugin>/<cmd>.toml for each of the 100 Claude Code
commands across 50 plugins, mapping /plugin:command to Gemini CLI's
TOML command format. Prompts are self-contained (no extension-relative
file inclusion) following confirmed patterns from real extension examples.
Includes generator script at tools/generate_gemini_commands.py.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: add ADRs for Phase A slash commands and Phase B distribution decision
- 2026-05-01-gemini-slash-commands.md: documents TOML format, directory
structure, self-contained prompt decision (no extension-relative @{path}),
and auto-discovery. Includes primary source citations.
- 2026-05-01-per-plugin-gemini-md-distribution.md: documents why per-plugin
GEMINI.md files are kept in the repo despite not auto-loading for extension
users. Refutes size/security liability claims with verified data.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: add integration planning document
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* refactor: remove per-plugin GEMINI.md files and generator (option C)
- Delete all 79 per-plugin GEMINI.md files (plugins/*/GEMINI.md)
- Delete per-plugin file generator (tools/generate_plugin_gemini_md.py)
- Eliminates false power user workflow benefit (files never auto-loaded)
- Keeps TOML slash commands for real discovery mechanism
- Single root GEMINI.md with bootstrap context remains
Rationale: Per-plugin files were in wrong location for Gemini CLI auto-discovery.
Power user benefit was fictional. Slash commands provide real discovery UX.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs(adr): update decisions to reflect Option C (removed per-plugin files)
ADR Updates:
- 2026-04-30-gemini-cli-integration.md: Explain Option C choice, document false power user claim
- 2026-05-01-gemini-slash-commands.md: Clarify slash commands are primary power user feature
- 2026-05-01-architecture-simplification.md (NEW): Document decision to remove per-plugin files
- docs/decisions/README.md: Updated to reflect final decision
- Archived: 2026-05-01-per-plugin-gemini-md-distribution.md
Rationale:
Audit revealed per-plugin GEMINI.md files don't auto-load (were positioned at root,
not in .gemini/ subdirectory). False power user benefit justification invalidated the
design. Slash commands (which do work) are the real power user feature.
Simplified architecture removes 79 files, 1 generator script, keeps all functionality.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: remove false power user claim from GEMINI.md, correct tool mapping doc, fix status claim
Critical fixes addressing three document contradictions:
1. GEMINI.md: Remove false auto-loading claim
- Line 42 claimed: 'Power users (repo cloned) | Auto-loaded when you cd plugins/<name>/'
- Audit + ADRs concluded this was INVALID (files never auto-loaded)
- Yet GEMINI.md still published the lie as fact
- Replaced with accurate description: slash commands are primary discovery mechanism
2. docs/gemini-tool-mapping.md: Correct slash commands status
- Listed slash commands as 'Claude Code only' without noting Gemini TOML support
- ADR 1 flagged: 'docs/gemini-tool-mapping.md requires correction (pending)'
- Correction never happened
- Updated to accurately describe Gemini's custom command support via TOML
- Clarified difference: Gemini has extension-specific commands, not global shortcuts
3. docs/decisions/README.md: Fix 'IMPLEMENTED' status claim
- Claimed: 'Status: IMPLEMENTED (2026-05-01)'
- Reality: All work on feature/gemini-cli-integration, not merged to main
- Main branch at c15b108 has zero Gemini files
- Changed to: 'Status: IN REVIEW' + noted 'Merged to main: NO'
These fixes ensure architecture docs match implementation reality.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs: add ADR and plan for Gemini CLI integration
* feat: add Stitch MCP server integration
- Configure Stitch MCP via HTTP endpoint (https://stitch.googleapis.com/mcp)
- Follows pattern from VSCode MCP config and factory template
- Enables AI-powered UI/UX design capabilities via Google Stitch
- MCP server type: http with standard Accept header
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chore: remove working notes and design process artifacts from repo
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* chore: remove invented top-level TOML commands with no Claude Code equivalent
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat: implement sync engine and protocol orchestrator for Gemini CLI
Upgraded the Gemini CLI integration to address maintenance and functional gaps identified during review.
Key Improvements:
- Protocol Orchestrator: Slash commands now treat Markdown files as executable protocols, achieving functional parity with Claude Code's interactive checkpoints and multi-step workflows.
- Sync Engine: Replaced the simple generator with a robust Python utility in tools/ that handles validation, pruning of stale TOMLs, and cross-platform path resolution.
- Local-Opt-In Workflow: Users can now selectively generate slash commands for specific plugins via the Makefile, eliminating repository drift.
- Fail-Safe Build Tools: Updated the Makefile with robust cleanup and sync targets.
- Documentation: Comprehensive updates to GEMINI.md and README.md, including a Windows compatibility guide (Git Bash/WSL).
PR Cleanup:
- Removed all 97+ derived TOML files and duplicates.
- Deleted all design process working notes and internal plans.
Strategic Note:
This PR provides the technical foundation for Gemini CLI support but defers to the maintainer on the directional decision of officially supporting multiple harnesses. All Gemini-specific features are designed to be lightweight and opt-in, preserving the core identity of the repository as a Claude Code marketplace.
* fix(gemini-tool-mapping): close unclosed code fence in skill migration template
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: address PR review feedback and consolidate Gemini CLI documentation
- Consolidated installation into a unified Quick Start section for Claude Code and Gemini CLI.
- Removed unused YouTube Design Extractor tool and associated Makefile targets.
- Corrected and synchronized plugin/agent/skill counts (81/185/153) across all documentation.
- Streamlined Gemini Skill Discovery Guide and removed redundant tool mapping reference.
- Hardened Makefile security by adding proper shell quoting to PLUGIN variable.
- Added Gemini CLI-specific uninstall and sync-commands examples.
* chore: remove .mcp.json and update plugin/agent counts
- Remove .mcp.json (personal MCP config, not for repo)
- Update CLAUDE.md and README.md counts to reflect current branch state
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs: finalize gemini-cli integration and sync plugin counts
- Restore original YouTube Design Extractor functionality in Makefile
- Add Gemini CLI extension targets to unified Makefile
- Restore standalone YouTube tool files (yt-design-extractor.py, requirements.txt)
- Sync all documentation (README, CLAUDE, GEMINI, docs/*) to 81-plugin state
- Align marketplace.json metadata description with 81-plugin reality
- Resolve all PR review threads and merge conflicts with main
* docs: revert out-of-scope documentation count synchronization
Reverts global plugin/agent/skill count updates across existing reference docs
(CLAUDE.md, README.md, docs/*) to match origin/main state. Gemini CLI
documentation remains focused on the integration itself.
* fix: restore plugin/agent counts in CLAUDE.md to match upstream
Counts were incorrectly lowered in a previous commit. Using upstream values
pending doc sync resolution in #517.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: revert marketplace.json drift, restore Makefile Options help block
- Revert .claude-plugin/marketplace.json to upstream (description text was drifted)
- Restore Options block (URL/INTERVAL/OUTPUT/ENGINE) in Makefile help target
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: restore upstream README.md content removed by drift
- Fix plugin count in Key Features: 81 → 80 (upstream value)
- Fix architecture diagram comment: 77 → 81 plugins (80 local + 1 external)
- Restore Troubleshooting section dropped in prior session
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* remove: docs/gemini-plugin-guide.md (not useful)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(gemini): update broken links after doc removal
* docs: add update, clean-commands, and uninstall workflows to Gemini CLI section
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: correct stale plugin/skill counts in gemini-extension.json and GEMINI.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Revert "fix: correct stale plugin/skill counts in gemini-extension.json and GEMINI.md"
This reverts commit 5a4a06d49f263d9eaa76a83d55b4141c8e4a0fc6.
* security: harden build tools and fix cross-platform paths
- Makefile: apply strict shell quoting to prevent command injection
- tools/generate_gemini_commands.py: rewrite using pathlib for Windows/Linux parity
- tools/generate_gemini_commands.py: add path validation to prevent traversal in pruning
- tools/generate_gemini_commands.py: add docstrings for maintainability
- GEMINI.md: fix numbering sequence in setup instructions
* docs(GEMINI): add Safety and System Integrity section
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): restore full Claude Code quick start into collapsible section
Original Step 1/Step 2 instructions were stripped to two lines. Restores
the complete content (plugin examples, explanatory text) inside the
recommended collapsible — no instructions removed, just reorganized.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): restore Claude Code intro, add Gemini CLI section, clarify scope
- Reverts all Gemini CLI parenthetical notes injected into Claude Code bullets
- Restores original wording (100 Commands, Install only what you need, etc.)
- Adds dedicated ## Gemini CLI section after Overview with its own feature list
- Retitles 'Plugins vs Agents' to clarify it is Claude Code only
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): use markdown bold in summary tags instead of <b>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Revert "docs(readme): use markdown bold in summary tags instead of <b>"
This reverts commit 19b879760f248e9e049f7f3dc83fbd23cf6c87d0.
* docs(GEMINI): reduce context bloat, remove duplicate sections
- Removed duplicate Slash Commands, How to Use Skills, and Common Skill
Categories sections (all repeated Navigation content)
- Replaced full Skill Library listing with a link to docs/plugins.md
- Removed stale metadata block and incorrect "already installed" claim
- 167 lines → 55: leaner per-prompt context overhead
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: correct extension directory path from 'agents' to 'claude-code-workflows'
Extension installs as claude-code-workflows, not agents. All cd paths
and TOML cleanup references in README and GEMINI.md were pointing to a
directory that does not exist.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): keep README Claude Code-first, badge links to GEMINI.md
- Remove ## Gemini CLI section and Gemini CLI Quick Start collapsible
- Unwrap Claude Code Quick Start from collapsible (back to original format)
- Restore 'Plugins vs Agents' heading (no Claude Code only qualifier needed)
- Add Gemini CLI badge next to Smithery badge pointing to GEMINI.md
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): add GitHub NOTE callout for Gemini CLI users
Badge alone is easy to miss. The [!NOTE] callout renders visually
distinct on GitHub and gives Gemini users enough context to find
GEMINI.md without disrupting Claude Code content.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix: sync counts to upstream and correct skill activation wording
- gemini-extension.json: 79 plugins/150+ skills → 80/153 (matches upstream)
- GEMINI.md: skills don't auto-activate silently; Gemini CLI asks first
- README callout: 'auto-discovered' → 'discoverable on-demand' (accurate)
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): add Gemini CLI entry to What's New section
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(readme): match What's New link style for Gemini CLI entry
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* docs(gemini): update comparison table for accuracy
* docs(gemini): correct command example prefix
* feat(gemini): improve sync engine to respect opt-in principle
- tools/generate_gemini_commands.py: only sync existing plugins by default (Smart Sync)
- tools/generate_gemini_commands.py: add --all flag for explicit full generation
- Makefile: update generate-all-commands to use --all
- Makefile: improve clean-commands to remove directories
* docs(gemini): audit and update GEMINI.md with high-fidelity counts and library summary
- Verified 80 plugins, 153 skills, 185 agents, and 100 commands against actual codebase.
- Re-added audited Skill Library summary for improved discovery.
- Corrected Plugin Catalog link and verified all technical examples.
- Reinforced Safety and System Integrity section.
* fix(GEMINI): replace colon-namespace syntax with flat Gemini slash command names
Gemini CLI does not support the /plugin:command namespace syntax used by
Claude Code. Updated Protocol Orchestrator example and Slash Commands
section to use flat /command-name format.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* revert: restore colon namespace syntax in GEMINI.md slash command examples
Gemini CLI derives command names from file paths — subdirectory separators
become colons, so commands/tdd-workflows/tdd-cycle.toml → /tdd-workflows:tdd-cycle.
The colon syntax is correct and matches the Claude Code namespace pattern.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: GitHub Copilot <noreply@github.com>
Co-authored-by: GitHub Copilot <copilot@github.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Pensyve is distributed from its own marketplace (major7apps/pensyve) so
version updates flow directly from the source. Reference it as a related
plugin in both the README and plugin reference doc with install commands.
Pensyve is now distributed exclusively from its own marketplace at
major7apps/pensyve. Removing the git-subdir entry from this marketplace
to avoid version drift (plugin.json in the subtree was stale vs the
source repo).
- Drop pensyve entry from .claude-plugin/marketplace.json
- Update plugin counts: 79 → 78, AI & ML 5 → 4
- Update docs/plugins.md and README.md accordingly
- README.md: three-tier model strategy now lists Opus 4.7; Tier 1
table entry and pricing bullet updated
- llm-application-dev README, ai-engineer agent, prompt-engineer agent:
Anthropic model list now reads Opus 4.7, Sonnet 4.6, Haiku 4.5
- plugin-eval judge.py: model map resolves "opus" tier to
claude-opus-4-7 (the ID the LLM judge layer hands to the SDK)
Sonnet 4.6 and Haiku 4.5 references left alone — those are the current
model versions for those tiers. Agent frontmatter is unaffected: all
184 agents already declare model as opus/sonnet/haiku/inherit, so the
new Opus version picks up automatically with no file changes.
- Counts now reflect 79 plugins (77 local + 2 external via git-subdir),
184 agents, 150 skills, 98 commands across 25 categories
- README/docs: add Governance category (protect-mcp), bump Testing to 2
(adds qa-orchestra), expand Security table to include reverse-engineering
and block-no-verify, add Protect MCP skills section, surface pensyve in
AI & ML
- marketplace.json: bump metadata to 1.6.0, bump pensyve to 1.2.0
- Add .github/workflows/validate.yml to gate PRs on:
- marketplace.json + every plugin.json + hooks.json parse as JSON
- every ./plugins/<name> source resolves on disk with a plugin.json
- plugin-eval pytest suite (would have caught the #482 sdk.stream bug class)
- README and docs now reflect 77 plugins / 182 agents / 149 skills / 96 commands
- agent-skills.md: add 9 missing plugin sections (agent-teams, reverse-engineering,
startup-business-analyst, shell-scripting, database-design, documentation-standards,
dotnet-contribution, plugin-eval, block-no-verify) covering 23 previously
undocumented skills; fix python-development from 5 to 16 skills
- plugins.md: correct 8 stale category counts and add missing Creative section
- agents.md: fix header from 100 to 182 agents
- architecture.md, usage.md: update plugin and skill counts
- README: surface HADS and block-no-verify in their categories, add 5 categories
that had been omitted (Creative, Accessibility, API, Utilities, Modernization)
Also a one-line follow-up to #462: team-composition-patterns/SKILL.md line 136
in the Troubleshooting section still referenced the old Task tool — updated to
the current Agent tool name.
- Add Pensyve memory plugin to marketplace via external GitHub source
- Update plugin/agent/skill/command counts across marketplace.json, CLAUDE.md, and README.md (75 plugins, 182 agents, 147 skills, 95 commands)
- Remove outdated PluginEval design spec and plan from docs/superpowers
- Bump marketplace version to 1.5.7
- Create CLAUDE.md with project conventions and PluginEval quick reference
- Add docs/plugin-eval.md with complete framework documentation (layers,
dimensions, scoring, anti-patterns, statistical methods, project structure)
- Add PluginEval section to main README under What's New
- Expand plugin-eval/README.md with quick start and command table
Plugin had inconsistent content (OpenAI references, CI/CD workflow baked
into review command). Replaced by official pr-review-toolkit and
comprehensive-review plugins. Also answered discussions #138, #421, #422.
- Claude Opus 4.5 → Opus 4.6, Claude Sonnet 4.5 → Sonnet 4.6 (Haiku stays 4.5)
- Update claude-sonnet-4-5 model IDs to claude-sonnet-4-6 in code examples
- Update SWE-bench stat from 80.9% to 80.8% for Opus 4.6
- Update GPT refs: GPT-5 → GPT-5.2, GPT-4o → gpt-5.2, GPT-4o-mini → GPT-5-mini
- Fix GPT-5.2-mini → GPT-5-mini (correct model name per OpenAI)
- Bump marketplace to v1.5.2 and affected plugin versions
Remove .mcp.json to eliminate external MCP dependency that likely caused plugin load failure.
Add tools: field to all agents, version: field to all skills, matching conductor plugin patterns.
* Add extra python skills covering code style, design patterns, resilience, resource management, testing patterns, and type safety ...etc
* fix: correct code examples in Python skills
- Clarify Python version requirements for type statement (3.10+ vs 3.12+)
- Add missing ValidationError import in configuration example
- Add missing httpx import and url parameter in async example
---------
Co-authored-by: Seth Hobson <wshobson@gmail.com>
Seth Hobson