caveman
claudeTalk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Puts the right rules in context on every prompt, automatically — built for full-stack developers moving across frontend, backend, and SQL in one session, researchers working in bare or LaTeX-only directories, and teams who want adversarial review (security red/blue team, code critic) before merge. 222 rules across 30 domains, retrieved by relevance rather than dumped into CLAUDE.md, plus a plan-approval gate, session security hardening, and per-codebase lessons memory. Requires Python 3.10+ on PATH.
Plugin clawness from marketplace clawness in fullymiddleaged/Clawness. Commands read from the repo's manifest — 19 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
addCreate a new Clawness rule from a natural language description. Describe what you want enforced and this will generate the YAML rule file with proper tags, triggers, and examples.
audit-rulesReview one domain of the Clawness rule corpus for correctness against current official documentation, then record what was established as a version stamp (applies_to / verified / sources) on each rule individually. For maintainers and fork maintainers. Reports verdicts and writes stamps; never rewri
bootstrapAuthor a starter set of Clawness rules for a project whose stack Clawness ships no corpus for (Ruby, PHP, Elixir, Haskell, C#, Swift, Dart, Scala, Clojure, ...). Researches the stack's current conventions from official documentation, drafts a small set of project rules into .clawness/rules/, lint-va
claude-mdShrink an oversized CLAUDE.md. Measures what the project's always-loaded instructions cost per turn, then works through it section by section — cutting what the codebase already says, moving path-specific guidance to .claude/rules/ and prompt-specific conventions to .clawness/rules/, and leaving loa
eval-setBuild and run a project-specific retrieval eval so changes to your rules or base prompt are scored, not eyeballed. Mirrors tests/ground_truth.json + `clawness eval`: you write prompt→expected-rule cases, then measure MRR@k and hit-rate before and after an edit. Run it after trimming a base prompt in
messagingWrite or rewrite the product's customer-facing copy — landing page, hero section, CTAs, onboarding, empty states, pricing, app-store and marketing pages — with the customer as the hero and the product as their guide. Scans the existing UI copy, drafts a one-page message brief (who the customer is, w
openclaw-auditTrim an OpenClaw workspace's base system prompt. Measures what the always-injected workspace files (SOUL.md, AGENTS.md, IDENTITY.md, USER.md, MEMORY.md) cost per turn, then works through them section by section — cutting what the tools or codebase already say, moving durable conventions to Clawness
perfRun a performance audit on the project or a specific module. Checks for N+1 queries, unnecessary re-renders, memory leaks, bundle size issues, and slow algorithms.
refreshBring this project's Clawness rules up to date with the framework version it actually runs. Establishes what is installed and what the codebase uses, looks up what changed since the rules were verified, and writes version-corrected overrides into .clawness/rules/ — reporting the list and stopping fo
reviewRun an adversarial code review on staged changes or a specific file. Spawns the code-critic agent to find bugs, performance issues, and missed edge cases. Use before merging PRs or committing.
security-auditRun a stateful red team / blue team security audit on the current project or a specific module. First enumerates the attack surface deterministically with `clawness scan` (zero LLM tokens, identical every run) and accumulates verdicts in a findings ledger, so each pass adjudicates only what is NEW i
statusShow the current Clawness configuration: which rules are loaded, which agents are available, and how the hook is configured. Use to understand what rules Claude is seeing for this project.
user-docsWrite user documentation for a project by scanning its codebase — its UI screens and its public API/CLI — inferring what someone can actually do with it, and drafting brief, task-oriented docs to the Diátaxis standard (tutorial / how-to / reference / explanation). Handles both non-technical end-user
vuln-huntHunt for new vulnerabilities in someone else's open-source code, as a defender heading for coordinated disclosure. Reads the project's threat model, enumerates the attack surface with `clawness scan` plus any installed SAST, runs variant analysis on the project's past security fixes, has the red tea
vuln-reportWrite a vulnerability report that is clear, short and ready to submit: a GitHub-advisory-shaped disclosure for maintainers (summary, affected versions, CVSS 4.0 vector, CWE, root cause at pinned file:line, minimal PoC, impact, suggested fix), or a one-page summary of a security audit. Every claim ci
arch-challengerDevil's advocate for architecture decisions. Use when proposing a new system design, choosing a technology, or making a significant structural change. Challenges assumptions and proposes alternatives.
code-criticAdversarial code reviewer. Use when you want a brutally honest review of code quality before a PR, merge, or deployment. Focuses on bugs, performance, maintainability, and missed edge cases. Read-only.
perf-auditorAnalyzes code for performance issues. Focuses on N+1 queries, unnecessary re-renders, memory leaks, bundle size, and slow algorithms. Use before deployment or when something feels slow.
refactor-advisorAnalyzes code for refactoring opportunities. Identifies code smells, duplications, overly complex functions, tight coupling, and suggests specific improvements. Read-only — reports findings, doesn't modify.
security-blue-teamUse after the red team has reported findings. Proposes concrete fixes, hardening measures, and defense-in-depth strategies. Reviews red team findings for false positives and prioritizes remediation by risk.
security-red-teamUse when reviewing code for security vulnerabilities. Thinks like an attacker. Searches for current CVEs and OWASP Top 10 issues relevant to the tech stack. Invoke for security audits, pre-deployment reviews, or when touching auth, payments, or user data.
test-writerGenerates comprehensive tests for code. Reads existing test patterns in the project and matches the style (Jest, Vitest, pytest, etc.). Covers happy paths, edge cases, error cases, and boundary conditions.
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/ensure_deps.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/git_check.py"; done; echo "[Clawness] Python 3.10+ was not found on PATH, so none of Clawness's
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/memory_init.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/handoff_check.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/handoff_autostart.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/stack_detect.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/changelog_check.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/claude_md_check.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/trust_ledger.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/claude_hook.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/compress_output.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/plan_gate.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/access_guard.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/plan_gate.py"; done; exit 0
for p in python3 python py; do command -v "$p" >/dev/null 2>&1 && exec "$p" "${CLAUDE_PLUGIN_ROOT}/hooks/access_guard.py"; done; exit 0
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.