Active PARA system management. Five skills cover folder organization, weekly review automation, Progressive Summarization, Hemingway Bridge session handoffs (integrates with rad-session), and the 12 Favorite Problems workshop. Two autonomous agents: para-auditor (structure validation) and para-weekly-reviewer (review briefings). One pure-stdlib Python validator (`audit-para-structure.py`) that mechanically enforces the four-canonical-folder rule (Projects/Areas/Resources/Archive), detects false projects (topic-shaped names instead of project-shaped), flags non-PARA anti-pattern folders (Inbox/Notes/Misc/etc.), counts active projects (warn >10, info >20, PARA recommends 5-10), and finds orphaned root files. Based on Tiago Forte's Building a Second Brain methodology.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Validates PARA folder structure for anti-patterns, detects topic-based organization, counts and evaluates active projects, identifies false projects, and checks for orphaned files outside the PARA hierarchy. Use this agent when the user says "audit my PARA", "check my folder structure", "is my system organized correctly", "validate my second brain", "find problems in my PARA", or wants a structural health check of their knowledge management system. <example> Context: The user suspects their PARA system has drifted from best practices. user: "Audit my PARA system — I think it's gotten messy" assistant: "I'll use the para-auditor agent to validate your folder structure and identify anti-patterns." <commentary> User requesting structural validation — the auditor scans for the specific anti-patterns that cause PARA systems to degrade: topic-based folders, false projects, orphaned files. </commentary> </example> <example> Context: The user just set up PARA and wants to verify they did it right. user: "Did I set up my PARA folders correctly?" assistant: "I'll use the para-auditor agent to validate your folder structure against PARA best practices." <commentary> New user verification — the auditor checks for exactly 4 top-level folders, correct naming, and no common setup mistakes. </commentary> </example> <example> Context: The user feels overwhelmed and suspects organizational problems. user: "Something is wrong with my system — I can never find anything" assistant: "I'll use the para-auditor agent to diagnose structural issues in your PARA system." <commentary> Diagnostic request — check for over-nesting, topic-based organization, folder explosion, and other patterns that make retrieval difficult. </commentary> </example>
Autonomous weekly review agent that scans a user's PARA folder structure, identifies stale projects, flags inbox overflow, and generates a structured review briefing. Use this agent when performing a weekly review, when the user says "run my weekly review", "scan my PARA system", "what needs attention", "review my projects", "check my second brain", or on a scheduled cron trigger. <example> Context: The user wants to run their weekly PARA review. user: "Run my weekly review" assistant: "I'll use the para-weekly-reviewer agent to scan your PARA folders and generate a review briefing." <commentary> User explicitly requesting a weekly review — trigger the agent to autonomously scan the PARA structure and produce actionable findings. </commentary> </example> <example> Context: The user feels their system is getting stale and wants a health check. user: "What needs attention in my second brain?" assistant: "I'll use the para-weekly-reviewer agent to identify stale projects, unprocessed captures, and areas needing attention." <commentary> User asking about system health — the weekly reviewer scans for staleness, inbox overflow, and neglected areas proactively. </commentary> </example> <example> Context: Cron-triggered or scheduled review at start of week. user: "It's Monday — time for my weekly review" assistant: "I'll use the para-weekly-reviewer agent to generate your weekly review briefing." <commentary> Scheduled or routine review trigger — generate a comprehensive briefing the user can work through during their review session. </commentary> </example>
This skill should be used when the user says "help me write this", "assemble my notes", "I have notes and need to create something", "intermediate packets", "archipelago of ideas", "I'm facing a blank page", "dial down the scope", "I'm overwhelmed by this project", "ship something smaller", "connect these ideas", "draft from my notes", "turn my research into output", or wants to assemble captured knowledge into creative output like articles, presentations, reports, or deliverables.
This skill should be used when the user says "hemingway bridge", "wrap up session", "save my progress", "where did I leave off", "session handoff", "end of session", "capture what I was working on", "pick up where I left off", "PARA handoff", "what should I do next session", or wants to capture session state in a PARA-aware format before stopping work. Integrates with rad-session's wrapup/startup cycle.
This skill should be used when the user says "organize my notes", "PARA method", "second brain", "set up PARA", "I'm overwhelmed with files", "productivity system", "knowledge management", "where does this go", "classify this note", "my system is broken", "digital organization", "clean slate", "project list", or wants to build, fix, or maintain a PARA-based knowledge management system. Covers PARA setup, classification, system diagnosis, and review workflows.
This skill should be used when the user says "summarize this note", "progressive summarization", "distill this", "bold the key points", "highlight the important parts", "executive summary", "layer 2", "layer 3", "layer 4", "make this scannable", "TL;DR this article", "distill my notes", or pastes a raw note, article, transcript, or long text and wants it condensed into layered, scannable summaries. Applies Tiago Forte's Progressive Summarization technique.
This skill should be used when the user says "12 favorite problems", "twelve favorite problems", "Feynman problems", "capture filter", "what should I save", "I save too much", "I don't know what to capture", "my captures are unfocused", "favorite problems workshop", "identify my problems", "what are my big questions", or wants to create, review, or use a list of guiding questions as a personal capture filter for their Second Brain.
Uses power tools
Uses Bash, Write, or Edit tools
A curated marketplace of plugins for Claude Code — Anthropic's agentic coding tool. The lineup focuses on capabilities that add value beyond Opus's baseline competence: workflow lifecycle, MCP-backed live operations, structured planning, honest AI-pattern auditing, and domain-specific tools where they earn their place.
Install everything at once or cherry-pick individual plugins.
RAD-Claude-Skills/
├── packages/ # Standalone npm packages
│ └── coolify-mcp/ # @radoriginllc/coolify-mcp — MCP server for Coolify API
├── plugins/ # Claude Code CLI & Desktop plugins (multi-skill bundles)
│ ├── rad-1password/ # 1Password CLI workflows — secret rotation, env injection, vault ops
│ ├── rad-a11y/ # WCAG 2.2 AA accessibility toolkit
│ ├── rad-brainstormer/ # Anti-anchoring brainstorming — any topic, not just code
│ ├── rad-chrome-extension/ # MV3 Chrome extension development
│ ├── rad-code-review/ # Diff-aware adversarial code review
│ ├── rad-context-prompter/ # Prompt, loop & goal engineering across the AI platform catalog
│ ├── rad-coolify-orchestrator/ # Coolify self-hosted PaaS management (MCP-backed)
│ ├── rad-explain/ # Honest project explanation — 5 skills + 2 grounding/overpromise validators
│ ├── rad-para-second-brain/ # PARA second brain — organize, review, distill
│ ├── rad-planner/ # Strictly-planning — risk-first, adversarial, mechanically-validated → docs/plan.md
│ ├── rad-seo-optimizer/ # Complete SEO & AEO toolkit
│ └── rad-repo-manager/ # Repo manager for vibe coders — startup/wrapup/repo-init/repo-align + drift hooks
└── skills/ # Claude.ai skills (ZIP upload / Project Knowledge)
├── rad-brainstormer/ # Ideation — Claude.ai adaptation of rad-brainstormer
├── rad-seo-aeo-reviewer/ # SEO/AEO — Claude.ai adaptation of rad-seo-optimizer
└── rad-writer/ # Writing — Claude.ai-only distribution (no longer a plugin)
You'll notice some names appear in both plugins/ and skills/ (rad-brainstormer, plus rad-seo-optimizer ↔ rad-seo-aeo-reviewer), and that rad-writer lives only under skills/. They cover the same knowledge but are built for different environments:
plugins/ — Claude Code CLI & Claude Desktop
Full plugin bundles with multiple skills, autonomous agents, reference files, and automatic routing. They activate when you're working in a Claude Code session — they can read your filesystem, spawn subagents, and chain tools together. Install with claude plugins add.
skills/ — Claude.ai (the web app)
Single-file skills designed for claude.ai. They work as uploadable ZIP files via Settings > Customize > Skills, as Project Knowledge, or as conversation attachments. They consolidate plugin knowledge into one skill, use web search and URL fetching instead of filesystem tools, and output deliverables as artifacts. No CLI needed.
Two plugins have Claude.ai counterparts: rad-brainstormer and rad-seo-optimizer (as rad-seo-aeo-reviewer). A third Claude.ai skill, rad-writer, is distributed standalone — the matching plugin was retired (its project-narrative role moved to rad-explain). The table column Works with shows which environments each plugin supports.
Claude Code handles most coding tasks well out of the box — but it doesn't know which MCP servers your project has wired up, which review patterns catch AI-generated mistakes in your specific framework, or how to deterministically validate the implementation plan it just generated. These plugins add value Opus doesn't provide on its own: deterministic validators (Python scripts), MCP-backed live operations, structured workflow lifecycle, and domain-specific tools.
Each one installs in a single command and activates automatically when you ask Claude about relevant topics. No configuration, no manual invocation. Use any plugin on its own, or run /rad-repo-manager:startup in a new project — it's a quick read-only orientation (the four active docs + git state + two mechanical drift scans); on a fresh repo it points you at /rad-repo-manager:repo-init, which scaffolds a lean AGENTS.md + agent shims + the four-doc core and hands off to /rad-planner:plan.
Add the entire marketplace to Claude Code or Claude Desktop — browse and install any plugin, with automatic updates on sync.
# Add the marketplace
claude plugin marketplace add https://github.com/RadOrigin-LLC/RAD-Claude-Skills
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub radorigin-llc/rad-claude-skills --plugin rad-para-second-brainCodebase-scoped SEO/AEO tooling for Claude Code with four pure-stdlib Python validators that turn the plugin's static-analysis claims into deterministic checks: `audit-ai-access.py` (per-AI-bot robots.txt allow/block matrix classed training vs citation — GPTBot, ClaudeBot, Google-Extended, CCBot vs OAI-SearchBot, ChatGPT-User, Claude-SearchBot/User, PerplexityBot/User, Bingbot, Googlebot — plus llms.txt existence/format check, Content-Signal/RSL/noai detection, JS-dependence heuristic, and optional CDN-block UA probing), `validate-jsonld.py` (extracts JSON-LD from HTML and framework source including dangerouslySetInnerHTML/set:html/template-literal forms, validates against ~20 SEO-impactful schema.org types, honest dynamic_jsonld findings for unverifiable JS-built blocks), `audit-meta-tags.py` (title/description lengths, canonical shape, charset, viewport, robots sanity, Open Graph 5-prop + Twitter Card 4-prop coverage, hreflang x-default), `check-broken-links.py` (parallel HEAD scanner with GET-Range fallback; URL list / sitemap / HTML-root inputs). Plus knowledge skills for AEO/GEO content optimization (with AI crawl-access gate and Lighthouse Agentic Browsing awareness), keyword ideation, content strategy, schema generation with 2026 rich-result deprecation awareness (FAQ/HowTo retired), E-E-A-T, and observable competitive research. Honest scope: does NOT measure numerical Core Web Vitals, keyword volumes, backlink profiles, or actual AI citation rates — those require Path B MCP integrations documented in references/CAPABILITIES.md.
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection, service worker lifecycle, React UI patterns, testing, and Chrome Web Store troubleshooting. The chrome-ext-reviewer agent runs two validators before LLM judgment: `audit-manifest.py` (manifest.json audit for MV3 compliance, permission overreach, weak CSP, web_accessible_resources scoping, MV2 leftovers, CWS-rejection causes; auto-discovers WXT `.output/` build manifests) and `scan-mv3-violations.py` (greps source for CSP-banned `eval` / `new Function` / `setTimeout('string')`, remote `<script src="http">` and dynamic imports of remote URLs, MV2-only `chrome.tabs.executeScript` / `chrome.browserAction` / `chrome.extension.getBackgroundPage`, blocking webRequest listeners, optional DOM-risk `innerHTML` / `document.write`). Both emit findings with severity and specific fix recommendations. Pure stdlib Python 3.8+.
3-role adversarial code review for Claude Code — Opus default, Sonnet/Haiku compatible. Parallel tool-call pipeline, JSON-first subagent output, compaction-safe checkpointing with `--resume`, and `--non-interactive` mode for agents/CI. Blame-aware diff scoping, 14-pattern AI slop detection (hallucinated imports, fake error handling, ghost type assertions, mock-shaped fallbacks, etc.), framework-specific IDOR for Next.js / Express / Fastify / Django / Rails / Go, WCAG 2.2 + dynamic ARIA state detection, performance heuristics, severity-ranked findings with release verdict, and accepted-risk expiry enforcement. Includes a `code-reviewer` agent for proactive autonomous review. v5.0: finding IDs shortened to `CR-NNN` (config/state paths unchanged); the hallucinated-imports validator is now wired into the automated-checks phase (offline, lockfile-verified, runs even in --local-only); history comparison matches findings across runs by fingerprint (category+file+title) instead of per-run IDs, making "show new findings only" trustworthy; the never-implemented `--engine claude|codex|both` flag removed in favor of the real `--adversarial-model <name>` cross-model challenge pass; reports save to `.radcr/history/` only (no loose root-level report file). Backed by `check-hallucinated-imports.py` — a pure-stdlib Python 3.8+ script that parses 9 lockfile formats (package-lock.json, yarn.lock, pnpm-lock.yaml, package.json deps, requirements.txt, pyproject.toml, Pipfile.lock, poetry.lock, uv.lock), extracts imports via Python `ast` + JS/TS regex, and flags packages not declared in any lockfile (slopsquatting risk). Runs standalone or in the orchestrator's Step 5g.
A repo manager for vibe coders — keeps a project's docs minimal, consistent, and honest so coding agents don't get confused or misled by contradictory information. It is the 'manager'; your coding agent is the 'employee.' Four skills, two of them deliberately lean: - `/startup` — orient at the start of a session: read the four active docs + git state, run the two cheap mechanical scans (loose docs, stale docs), surface where you are + what's next + whether the docs are trustworthy. Read-only; recommends `/repo-init` on a fresh repo or `/repo-align` when the scans show drift. - `/wrapup` — leave a clean handoff for a new chat or a post-compaction continuation. Overwrites `docs/handoff.md` from git evidence (not chat memory), then reconciles the active core docs with the session — applying scoped updates to the docs it owns (`docs/plan.md`, AGENTS.md operational sections) on your OK, and drafting exact edits to stale user-owned docs (prd/design/decisions) applied only on per-edit confirmation. Ends with a one-line hygiene pulse. No status/roadmap files, no auto-commit, never runs tests. - `/repo-init` — first-run setup: scaffold the compact doc model (core docs, thin agent shims, minimal folders) on a new or nearly empty repo. Creates only what's missing; never invents product content; never overwrites user-authored files without confirmation. - `/repo-align` — the opt-in deep clean: find drift (contradictions, redundancy, stale/loose/misplaced docs, broken read paths) and propose fixes interactively. Proposes — never auto-acts; moves tracked files with `git mv` to preserve history. Plus an ambient hook layer (Claude Code-only, silent in repos that don't use the doc model, never blocking, says nothing on green): SessionStart injects a one-line doc-health note when something is stale or loose; PreCompact preserves the handoff's raw material (validation results, files changed, next action) through compaction; Stop reminds about wrapup at most once per session when real work is uncommitted and the handoff isn't fresh. The doc model is a tiny, declared, defended core — `AGENTS.md`, `docs/prd.md`, `docs/plan.md`, `docs/handoff.md` (prd/plan/handoff carry an `**Updated:**` freshness stamp) — plus conditional `docs/design.md`, a closed `docs/reference/` catalog, and `docs/archive/` for history. The boundary that matters: `docs/plan.md` owns the durable roadmap/scope/gates/stop-conditions; `docs/handoff.md` owns only the short resume snapshot for the next chat. The plugin authors `AGENTS.md` operational sections, the `CLAUDE.md`/`GEMINI.md` shims, and `docs/handoff.md`; durable changes (prd, design, decision-log) are drafted as exact edits and applied only on your explicit per-edit confirmation. Five pure-stdlib validators: the cheap pair (`repo-scan`, `doc-freshness`) runs every session; the deep trio (`doc-contradiction`, `doc-redundancy`, `audit-user-content`) runs in `repo-align`. Replaces rad-session; Claude-side counterpart to the Codex rad-repo-manager skills. Pairs with rad-planner (which owns `docs/plan.md` content and can birth `docs/prd.md` from its discovery interview; wrapup recommends `/rad-planner:replan` when plan divergence is structural rather than restructuring it itself); works standalone.
A council of cognitive-framework advisors that debates any decision — repo plans, website designs, product/codebase critiques, marketing plans, anything — then votes and returns one ranked, confidence-rated recommendation with dissent preserved and a single concrete next step. Diversity comes from incompatible *reasoning lenses* (The Contrarian, First Principles, The Vulcan, The Metric, The Storyteller, The Outsider, The Executor, The Orator, The Expansionist, The Growth Catalyst), not personas — research shows cognitive frameworks beat roleplay, and that perspective diversity (not debate depth) is the dominant driver of quality. One skill, `convene`, with two modes: `standard` (independent drafts → one blind peer-review round + dot-vote → rigor-weighted synthesis) and `quick` (parallel critics → synthesis, no review round). A Blue Hat orchestrator auto-selects 3–5 seats for any topic by engineering natural tension between opposing lenses (hard cap 5). Synthesis weights by empirical rigor and logical consistency — never headcount — preserves genuine clashes, rates confidence 1–10, and commits to exactly one next step (disagree-and-commit). Guardrails are baked in against the documented failure modes of multi-agent debate: conformity drift (independent generation), sycophancy (framework constraints, not personas), false consensus (preserved dissent), and runaway cost (hard agent/round caps + effort scaling). Claude-only — no external API keys. Output is one self-contained markdown report, delivered where you choose, never auto-committed. Pairs with rad-brainstormer (diverge → converge) and rad-planner (decide → sequence); recommends rad-code-review for deep code passes rather than duplicating it.
AI-powered development tools for code review, research, design, and workflow automation.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.