Agent Plugins Marketplace
All plugins

growmax-skills

v1.24.0

Growmax team Claude Code skills and workflows. Auto-discovers skills/, commands/, agents/, and hooks/. Ships: github-repo-analyzer (skill); terse-mode (skill — low-token terse reply style, in-house alternative to caveman-style compressors; trigger with 'terse mode'/'be terse'/'caveman mode', levels lite|full|off); learn-app + product-manager (per-repo product notebook — /learn-app builds and maintains docs/product/ from a code census + optional read-only walk, with an async question ledger the human answers in-file; the product-manager agent answers questions and writes specs from the notebook with per-claim provenance, never inventing product truth); feature-review (end-of-development multi-agent review — TDD compliance, contextual-creation UX, UI-standards compliance (compose-never-fork + tokens, per .claude/UI-STANDARDS.md), 10k-row scalability + security sweep, advisory architecture ideas — one verified scorecard with a per-finding HIGH/MEDIUM/LOW confidence report, a run ledger, and a periodic-calibration process for improving precision over time); ux-audit + ux-migrate (census UI drift against the repo's UI standard into an approvable backlog, then pay it down autonomously by composing shared components — mirrors e2e-map + e2e-batch; a write-time hook nudges the mechanical rules for free); ui-builder (pre-build shared-component resolver — /ui-builder maps a UI request to the exact shared component per .claude/UI-STANDARDS.md Table 1 with a reuse/extend/new verdict BEFORE code is written; ships the ui-builder-resolver agent and a prompt-time reminder hook, gated to repos that ship the rulebook); app-cartograph (map a live app into durable context — navigation + business flows + knowledge graph — via a code-seeded frontier and a write-safe human-in-the-loop walk; runs upstream of E2E); e2e-flow (gated multi-agent E2E test-generation for a single flow, web + api); e2e-map + e2e-batch (whole-app flow census → one approval → autonomous suite generation); and the bug-fix pipeline: confirm-bug (turn a raw bug report into a human-confirmed RED reproduction — read-only diagnosis with a cross-surface divergence table and ranked root causes, a human ruling on correct behavior, then a deterministic env-gated failing spec + repro/BUG-id/ contract that is frozen as the grader; reports UNREPRODUCIBLE instead of faking a red), fix-bug (fix the root cause against that frozen grader in a fresh session, then have an independent read-only validator grade it — 'fixed' requires the runner green AND the named assertion actually passing AND the repro byte-identical to its confirmed commit; on PASS the repro is promoted out of its env gate into a permanent regression test), bugfix (the whole lap as ONE command — a thin chain of confirm-bug into fix-bug, same three interrupts; safe because context isolation lives in the subagents and grader integrity in the pushed tag, not in session boundaries), and validate-fix (the same grader standalone, for a fix you didn't watch or as a CI check — default FAIL, and an edited repro fails regardless of how green the run is). The pipeline holds a 3-interrupt budget per bug (ruling+strategy · confirm-red · ship): a risk tier tunes rigor instead of adding gates, repros are matrices (boundary + cross-tenant rows, not one case), and a mechanical mutation check proves the repro would fail without the fix — assurance that costs no human attention. The graders are themselves adversarially evaluated: regression/bugfix-pipeline/ ships a zero-dependency fixture app and four eval cases — reproducible, unreproducible, a counterfeit fix branching on the repro's env gate, and a repro tampered after confirmation — plus a protect-repro PreToolUse hook (self-tested) and a pushed confirmation tag (repro-BUG-id) as the validator's tamper-proof baseline. gmax (the agentic-development operating layer): /gmax-setup installs 6 personas + 7 skills + standards + workflow.config.md into any project non-destructively — one gated spine (understand → design → plan → build waves → senior review) with three human gates; detects the project's EXISTING knowledge base and points at it, never creates one; /gmax-update refreshes only the canonical files via .gmax-version diffing, never touching project-filled config, standards, or KB; harness shims for Claude Code + OpenCode, zero-shim for Hermes; regression-covered at regression/gmax-setup/.

Claude Code4 Skills

By Growmax0 GitHub starsUpdated 2 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
4 skill or MCP entries
Source updated
Aug 27, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology

Install plugin

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install growmax-skills@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/growmax/growmax-skills

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.

Plugin files

growmax-skills/
├── .claude-plugin/plugin.json
├── skills/github-repo-analyzer/SKILL.md
├── skills/plain-explainer/SKILL.md
├── skills/terse-mode/SKILL.md
└── skills/ui-builder/SKILL.md

Included Skills4

github-repo-analyzerskills/github-repo-analyzer/SKILL.md

Analyze any GitHub repository end-to-end: what it is, the problem it solves, why it's used, what's happening with it now, and what Growmax would gain by adopting it — plus a two-part "is it safe to use?" verdict: (1) LICENSE (is it open source, what license, can a commercial closed-source B2B SaaS like Growmax use it) and (2) SECURITY from a Trivy scan (known CVEs in dependencies, hardcoded secrets, IaC misconfigs). Use whenever the user shares a GitHub URL or asks about a repo, library, tool, package, or dependency. Trigger on "what is this repo", "should we use/adopt Y", "can we use this at Growmax", "is this safe to use", "is it secure", "scan this repo", "any CVEs / vulnerabilities", "run a trivy scan", "is this open source", or "what license does X have" — even without the words "analyze", "license", or "security". Prefer this over answering from memory: repos change, and license terms and vulnerabilities must be read from the actual repo.

plain-explainerskills/plain-explainer/SKILL.md

Answer "explain X", "what is X", "what's X", "tell me about X", "can you explain about this", or "ELI5" requests with a plain, honest, understandable- on-the-first-read explanation — so the user NEVER has to follow up with "now explain it in simple terms." Strip marketing hype and buzzwords and say what the thing ACTUALLY is and does, especially for products, tools, companies, frameworks, libraries, or trendy tech terms where online sources oversell and the marketing is louder than the real picture. Use this whenever the user asks you to explain, define, or describe something, or asks what something is or does — even if they don't say "simply" or "briefly." Plain-and-honest is the DEFAULT here, not something the user should have to ask for a second time.

terse-modeskills/terse-mode/SKILL.md

Switch this session's replies to a terse, low-token output style — same technical content, far fewer words — without any third-party plugin. Growmax's in-house alternative to "caveman"-style compressors: near-zero per-turn overhead, code and commands stay byte-exact. Use when the user says "terse mode", "be terse", "short answers", "caveman mode", "save tokens", "stop being verbose", "tl;dr mode", or invokes /terse-mode [lite|full|off]. Stays on for the rest of the session until the user says "normal mode" or "/terse-mode off".

ui-builderskills/ui-builder/SKILL.md

Before building ANY apps/web-vite UI, resolve a UI request to the exact shared component to reuse. Reads the rulebook (.claude/UI-STANDARDS.md Table 1 region→component, Table 0 paths, Table 2 icons, Table 3 tokens) and returns: the shared component to compose, the Part A rules that apply, and a CMP-5 verdict (reuse / extend / new). Read-only — points, never writes. Use whenever a prompt asks to create/add/build a page, screen, table, form, list, header, dialog, filter, chart, or any web-admin UI element.

Plugin manifests1

.claude-plugin/plugin.json
{
  "name": "growmax-skills",
  "version": "1.24.0",
  "description": "Growmax team Claude Code skills and workflows. Auto-discovers skills/, commands/, agents/, and hooks/. Ships: github-repo-analyzer (skill); terse-mode (skill — low-token terse reply style, in-house alternative to caveman-style compressors; trigger with 'terse mode'/'be terse'/'caveman mode', levels lite|full|off); learn-app + product-manager (per-repo product notebook — /learn-app builds and maintains docs/product/ from a code census + optional read-only walk, with an async question ledger the human answers in-file; the product-manager agent answers questions and writes specs from the notebook with per-claim provenance, never inventing product truth); feature-review (end-of-development multi-agent review — TDD compliance, contextual-creation UX, UI-standards compliance (compose-never-fork + tokens, per .claude/UI-STANDARDS.md), 10k-row scalability + security sweep, advisory architecture ideas — one verified scorecard with a per-finding HIGH/MEDIUM/LOW confidence report, a run ledger, and a periodic-calibration process for improving precision over time); ux-audit + ux-migrate (census UI drift against the repo's UI standard into an approvable backlog, then pay it down autonomously by composing shared components — mirrors e2e-map + e2e-batch; a write-time hook nudges the mechanical rules for free); ui-builder (pre-build shared-component resolver — /ui-builder maps a UI request to the exact shared component per .claude/UI-STANDARDS.md Table 1 with a reuse/extend/new verdict BEFORE code is written; ships the ui-builder-resolver agent and a prompt-time reminder hook, gated to repos that ship the rulebook); app-cartograph (map a live app into durable context — navigation + business flows + knowledge graph — via a code-seeded frontier and a write-safe human-in-the-loop walk; runs upstream of E2E); e2e-flow (gated multi-agent E2E test-generation for a single flow, web + api); e2e-map + e2e-batch (whole-app flow census → one approval → autonomous suite generation); and the bug-fix pipeline: confirm-bug (turn a raw bug report into a human-confirmed RED reproduction — read-only diagnosis with a cross-surface divergence table and ranked root causes, a human ruling on correct behavior, then a deterministic env-gated failing spec + repro/BUG-id/ contract that is frozen as the grader; reports UNREPRODUCIBLE instead of faking a red), fix-bug (fix the root cause against that frozen grader in a fresh session, then have an independent read-only validator grade it — 'fixed' requires the runner green AND the named assertion actually passing AND the repro byte-identical to its confirmed commit; on PASS the repro is promoted out of its env gate into a permanent regression test), bugfix (the whole lap as ONE command — a thin chain of confirm-bug into fix-bug, same three interrupts; safe because context isolation lives in the subagents and grader integrity in the pushed tag, not in session boundaries), and validate-fix (the same grader standalone, for a fix you didn't watch or as a CI check — default FAIL, and an edited repro fails regardless of how green the run is). The pipeline holds a 3-interrupt budget per bug (ruling+strategy · confirm-red · ship): a risk tier tunes rigor instead of adding gates, repros are matrices (boundary + cross-tenant rows, not one case), and a mechanical mutation check proves the repro would fail without the fix — assurance that costs no human attention. The graders are themselves adversarially evaluated: regression/bugfix-pipeline/ ships a zero-dependency fixture app and four eval cases — reproducible, unreproducible, a counterfeit fix branching on the repro's env gate, and a repro tampered after confirmation — plus a protect-repro PreToolUse hook (self-tested) and a pushed confirmation tag (repro-BUG-id) as the validator's tamper-proof baseline. gmax (the agentic-development operating layer): /gmax-setup installs 6 personas + 7 skills + standards + workflow.config.md into any project non-destructively — one gated spine (understand → design → plan → build waves → senior review) with three human gates; detects the project's EXISTING knowledge base and points at it, never creates one; /gmax-update refreshes only the canonical files via .gmax-version diffing, never touching project-filled config, standards, or KB; harness shims for Claude Code + OpenCode, zero-shim for Hermes; regression-covered at regression/gmax-setup/.",
  "author": {
    "name": "Growmax"
  },
  "homepage": "https://github.com/growmax/growmax-skills"
}

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[growmax-skills on Agent Plugins Marketplace](https://pluginsmp.com/plugins/growmax-skills)