Skip to content

borghei/Claude-Skills / engineering/claude-code-mastery

claude-code-mastery

Flagged

Optimizes CLAUDE.md files, scaffolds skills and subagents, wires hooks and measures context budget for Claude Code. Use when writing or trimming a CLAUDE.md, creating a skill, subagent or hook, or auditing token usage.

FileKindSize
SKILL.mdskill md8.4 KB
assets/agent-template.mdmarkdown3.2 KB
assets/skill-template.mdmarkdown3.9 KB
references/hooks-cookbook.mdmarkdown19.5 KB
references/quick-reference.mdmarkdown3.7 KB
references/skill-authoring-guide.mdmarkdown15.0 KB
references/subagent-patterns.mdmarkdown19.2 KB
references/tool-reference.mdmarkdown5.7 KB
references/workflows.mdmarkdown5.5 KB
scripts/claudemd_optimizer.pyexecutablescript19.7 KB
scripts/context_analyzer.pyexecutablescript14.8 KB
scripts/skill_scaffolder.pyexecutablescript11.7 KB

assets/skill-template.md

View on GitHub
---
name: your-skill-name
description: >-
  This skill should be used when the user asks to "action one",
  "action two", "action three", or "action four". Use for
  domain-specific workflows, analysis, and automation.
license: MIT
metadata:
  version: 1.0.0
  category: engineering
  domain: your-domain
---

# Your Skill Title

One-line summary of what this skill provides and who benefits from it.

## Keywords

keyword1, keyword2, keyword3, keyword4, keyword5,
action-verb1, action-verb2, domain-term1, domain-term2

---

## Table of Contents

- [Quick Start](#quick-start)
- [Tools Overview](#tools-overview)
  - [Tool One](#1-tool-one)
  - [Tool Two](#2-tool-two)
- [Workflows](#workflows)
  - [Primary Workflow](#workflow-1-primary-workflow)
  - [Secondary Workflow](#workflow-2-secondary-workflow)
- [Reference Documentation](#reference-documentation)
- [Quick Reference](#quick-reference)

---

## Quick Start

```bash
# Primary tool - basic usage
python scripts/tool_one.py input_file.txt

# Primary tool - with options
python scripts/tool_one.py input_file.txt --option value --json

# Secondary tool
python scripts/tool_two.py /path/to/dir --format table
```

---

## Tools Overview

### 1. Tool One

Brief description of what this tool does and when to use it.

```bash
# Basic usage
python scripts/tool_one.py input

# With options
python scripts/tool_one.py input --option value

# JSON output for piping
python scripts/tool_one.py input --json
```

| Parameter | Description |
|-----------|-------------|
| `input` | Description of the input parameter |
| `--option, -o` | Description of the option (default: value) |
| `--format` | Output format: table, json, csv (default: table) |
| `--json` | Output in JSON format |

**Example output:**

```
Tool One Report
================
  Input:   example.txt
  Status:  Analyzed
  Score:   85/100

Findings:
  1. Finding description (severity)
  2. Finding description (severity)
```

### 2. Tool Two

Brief description of what this tool does and when to use it.

```bash
python scripts/tool_two.py /path/to/dir
python scripts/tool_two.py /path/to/dir --depth 3 --json
```

| Parameter | Description |
|-----------|-------------|
| `path` | Directory path to analyze |
| `--depth, -d` | Analysis depth (default: 5) |
| `--json` | Output in JSON format |

---

## Workflows

### Workflow 1: Primary Workflow

Description of when and why to use this workflow.

**Step 1: Analyze the Current State**

```bash
python scripts/tool_one.py target --json > analysis.json
```

Review the output and identify areas that need attention.

**Step 2: Apply Changes**

Based on the analysis, take the following actions:

- Action based on finding type A
- Action based on finding type B
- Action based on finding type C

**Step 3: Validate**

```bash
python scripts/tool_one.py target --json
```

Verify the score has improved and no regressions were introduced.

### Workflow 2: Secondary Workflow

Description of the secondary use case.

**Step 1: Setup**

```bash
python scripts/tool_two.py /path/to/project
```

**Step 2: Execute**

Follow the recommendations from the tool output.

**Step 3: Verify**

Re-run the tool and confirm improvements.

---

## Reference Documentation

| Document | Path | When to Use |
|----------|------|-------------|
| Deep Guide | [references/guide.md](references/guide.md) | Detailed patterns and strategies |
| Examples | [references/examples.md](references/examples.md) | Real-world usage examples |

---

## Quick Reference

### Common Commands

| Task | Command |
|------|---------|
| Basic analysis | `python scripts/tool_one.py input` |
| JSON output | `python scripts/tool_one.py input --json` |
| Directory scan | `python scripts/tool_two.py /path` |
| Help | `python scripts/tool_one.py --help` |

### Decision Matrix

| Situation | Use This | Because |
|-----------|----------|---------|
| Scenario A | Tool One | Reason |
| Scenario B | Tool Two | Reason |
| Scenario C | Workflow 1 | Reason |

---

**Last Updated:** Month Year
**Version:** 1.0.0
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall