everything-claude-code-harness

aradotso/trending-skills · updated May 20, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/aradotso/trending-skills --skill everything-claude-code-harness
0 commentsdiscussion
summary

Skill by ara.so — Daily 2026 Skills collection.

skill.md

Everything Claude Code (ECC) — Agent Harness Performance System

Skill by ara.so — Daily 2026 Skills collection.

Everything Claude Code (ECC) is a production-ready performance optimization system for AI agent harnesses. It provides specialized subagents, reusable skills, custom slash commands, memory-persisting hooks, security scanning, and language-specific rules — all evolved from 10+ months of daily real-world use. Works across Claude Code, Cursor, Codex, OpenCode, and Antigravity.


Installation

Option 1: Plugin Marketplace (Recommended)

# Inside Claude Code, run:
/plugin marketplace add affaan-m/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

Option 2: Manual Clone

git clone https://github.com/affaan-m/everything-claude-code.git
cd everything-claude-code

# Install rules for your language stack
./install.sh typescript
# Multiple languages:
./install.sh typescript python golang swift
# Target a specific IDE:
./install.sh --target cursor typescript

Install Rules (Always Required)

Claude Code plugins cannot auto-distribute rules — install them manually via ./install.sh or copy from rules/ into your project's .claude/rules/ directory.


Directory Structure

everything-claude-code/
├── .claude-plugin/         # Plugin and marketplace manifests
│   ├── plugin.json
│   └── marketplace.json
├── agents/                 # Specialized subagents (planner, architect, etc.)
├── commands/               # Slash commands (/plan, /security-scan, etc.)
├── skills/                 # Reusable skill modules
├── hooks/                  # Lifecycle hooks (SessionStart, Stop, PostEdit, etc.)
├── rules/
│   ├── common/             # Language-agnostic rules
│   ├── typescript/
│   ├── python/
│   ├── golang/
│   └── swift/
├── scripts/                # Setup and utility scripts
└── install.sh              # Interactive installer

Key Commands

After installation, use the namespaced form (plugin install) or short form (manual install):

# Planning & architecture
/everything-claude-code:plan "Add OAuth2 login flow"
/everything-claude-code:architect "Design a multi-tenant SaaS system"

# Research-first development
/everything-claude-code:research "Best approach for rate limiting in Node.js"

# Security
/everything-claude-code:security-scan
/everything-claude-code:harness-audit

# Agent loops and orchestration
/everything-claude-code:loop-start
/everything-claude-code:loop-status
/everything-claude-code:quality-gate
/everything-claude-code:model-route

# Multi-agent workflows
/everything-claude-code:multi-plan
/everything-claude-code:multi-execute
/everything-claude-code:multi-backend
/everything-claude-code:multi-frontend

# Session and memory
/everything-claude-code:sessions
/everything-claude-code:instinct-import

# PM2 orchestration
/everything-claude-code:pm2

# Package manager setup
/everything-claude-code:setup-pm

With manual install, drop the everything-claude-code: prefix: /plan, /sessions, etc.


Hook Runtime Controls

ECC hooks fire at agent lifecycle events. Control strictness at runtime without editing files:

# Set hook strictness profile
export ECC_HOOK_PROFILE=minimal    # Least intrusive
export ECC_HOOK_PROFILE=standard   # Default
export ECC_HOOK_PROFILE=strict     # Maximum enforcement

# Disable specific hooks by ID (comma-separated)
export ECC_DISABLED_HOOKS="pre:bash:tmux-reminder,post:edit:typecheck"

Hook events covered: SessionStart, Stop, PostEdit, PreBash, PostBash, and more.


Package Manager Detection

ECC auto-detects your package manager with this priority chain:

  1. CLAUDE_PACKAGE_MANAGER environment variable
  2. .claude/package-manager.json (project-level)
  3. package.jsonpackageManager field
  4. Lock file detection (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb)
  5. ~/.claude/package-manager.json (global)
  6. First available manager as fallback
# Set via environment
export CLAUDE_PACKAGE_MANAGER=pnpm

# Set globally
node scripts/setup-package-manager.js --global pnpm

# Set per-project
node scripts/setup-package-manager.js --project bun

# Detect current setting
node scripts/setup-package-manager.js --detect

Skills System

Skills are markdown modules the agent loads to gain domain expertise. Install individually or in bulk.

Using a Skill

# Reference a skill explicitly in your prompt
"Use the search-first skill to find the right caching approach before implementing"

# Or trigger via slash command
/everything-claude-code:research "content hashing strategies for API responses"

Notable Built-in Skills

Skill Purpose
search-first Research before coding — avoids hallucinated APIs
cost-aware-llm-pipeline Optimizes token spend across model calls
content-hash-cache-pattern Cache invalidation via content hashing
skill-stocktake Audits which skills are loaded and active
frontend-slides Zero-dependency HTML presentation builder
configure-ecc Guided interactive ECC setup wizard
swift-actor-persistence Swift concurrency + persistence patterns
regex-vs-llm-structured-text Decides when to use regex vs LLM parsing

Writing a Custom Skill

Create skills/my-skill.md:

---
name: my-skill
description: What this skill does
triggers:
  - "phrase that activates this skill"
---

# My Skill

## When to Use
...

## Pattern
\`\`\`typescript
// concrete example
\`\`\`

## Rules
- Rule one
- Rule two

Instincts System (Continuous Learning)

Instincts are session-extracted patterns saved for reuse. They carry confidence scores and evolve over time.

Export an Instinct

/everything-claude-code:instinct-import

Instinct File Format

---
name: prefer-zod-for-validation
confidence: 0.92
extracted_from: session-2026-02-14
---

# Action
Always use Zod for runtime schema validation in TypeScript projects.

# Evidence
Caught 3 runtime type errors that TypeScript alone missed during session.

# Examples
\`\`\`typescript
import { z } from 'zod'

const UserSchema = z.object({
  id: z.string().uuid(),
  email: z.string().email(),
  role: z.enum(['admin', 'user'])
})

type User = z.infer<typeof UserSchema>
\`\`\`

Rules Architecture

Rules enforce coding standards per language. Install only what your stack needs.

# TypeScript + Python
./install.sh typescript python

# Check what's installed
ls .claude/rules/

Rule Directory Layout

rules/
├── common/         # Applies to all languages
│   ├── research-first.md
│   ├── security-baseline.md
│   └── verification-loops.md
├── typescript/
│   ├── no-any.md
│   ├── zod-validation.md
│   └── strict-mode.md
├── python/
│   ├── type-hints.md
│   └── django-patterns.md
└── golang/
    └── error-wrapping.md

Agents (Subagent Delegation)

Agents are specialized personas the orchestrator delegates to:

# In your prompt, reference an agent explicitly
"Delegate architecture decisions to the architect agent"
"Use the planner agent to break this feature into tasks"

Available agents include: planner, architect, researcher, verifier, security-auditor, and more. Each lives in agents/<name>.md with its own system prompt, tools list, and constraints.


AgentShield Security Scanning

Run security scans directly from Claude Code:

/everything-claude-code:security-scan

This invokes the AgentShield scanner (1282 tests, 102 rules) against your codebase and surfaces:

  • Hardcoded secrets
  • Injection vulnerabilities
  • Insecure dependencies
  • Agent prompt injection patterns

Memory Persistence Hooks

ECC hooks automatically save and restore session context:

// hooks/session-start.js — loads prior context on new session
const fs = require('fs')
const path = require('path')

const memoryPath = path.join(process.env.HOME, '.claude', 'session-memory.json')

if (fs.existsSync(memoryPath)) {
  const memory = JSON.parse(fs.readFileSync(memoryPath, 'utf8'))
  console.log('Restored session context:', memory.summary)
}
// hooks/stop.js — saves session summary on exit
const summary = {
  timestamp: new Date().toISOString(),
  summary: process.env.ECC_SESSION_SUMMARY 
how to use everything-claude-code-harness

How to use everything-claude-code-harness on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add everything-claude-code-harness
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/aradotso/trending-skills --skill everything-claude-code-harness

The skills CLI fetches everything-claude-code-harness from GitHub repository aradotso/trending-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/everything-claude-code-harness

Reload or restart Cursor to activate everything-claude-code-harness. Access the skill through slash commands (e.g., /everything-claude-code-harness) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.442 reviews
  • Pratham Ware· Dec 28, 2024

    Useful defaults in everything-claude-code-harness — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Kwame Flores· Dec 28, 2024

    everything-claude-code-harness has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Shikha Mishra· Dec 12, 2024

    everything-claude-code-harness reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Iyer· Nov 19, 2024

    everything-claude-code-harness fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ama Sethi· Oct 10, 2024

    We added everything-claude-code-harness from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kabir Martinez· Sep 9, 2024

    everything-claude-code-harness fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Carlos Diallo· Sep 5, 2024

    I recommend everything-claude-code-harness for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Kwame Kim· Sep 1, 2024

    everything-claude-code-harness reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ama Gill· Aug 28, 2024

    We added everything-claude-code-harness from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hana Diallo· Aug 24, 2024

    Useful defaults in everything-claude-code-harness — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 42

1 / 5