Skip to content

guanyang/open-agent-hub / template

replace-with-skill-name-using-hyphens

Verified

Use when [describe triggering conditions, symptoms, or specific errors].

FileKindSize
SKILL.mdskill md2.2 KB
---
name: replace-with-skill-name-using-hyphens
# CRITICAL: Description MUST describe "When to use" (triggers, symptoms, errors).
# NEVER summarize the skill's workflow here. Keep under 500 chars if possible.
description: Use when [describe triggering conditions, symptoms, or specific errors]. 
---

# Skill Name

## Overview
[1-2 sentences explaining the core principle. What is the fundamental insight of this skill?]

## When to Use (Triggers)
- **Symptoms**: [Errors, behaviors, or patterns that indicate this skill is needed]
- **Contexts**: [Specific scenarios where this pattern applies]

### When NOT to Use
- [Scenario A] -> Use `[other-skill-name]` instead.
- [Scenario B] -> Does not apply because...

## Core Pattern
[Explain the mental model. Use a before/after code block or a small `dot` flowchart if the decision process is non-obvious.]

```language
// ❌ Anti-pattern / Baseline failure
[Show the common mistake or naive approach]
```

```language
// ✅ Best practice / Correct implementation
[Show the correct pattern]
```

## Step-by-Step Workflow
[Clear, numbered steps for the agent to follow. Use imperative verbs.]

1. **[Phase 1]**: [Action to take]
2. **[Phase 2]**: [Action to take]
   - *Requirement*: [Specific constraint]
3. **[Phase 3]**: [Action to take]

## Quick Reference
[A table for fast lookup of commands, syntax, or common operations.]

| Operation / Scenario | Syntax / Command | Notes |
|----------------------|------------------|-------|
| [Operation]          | `[Command]`      | [Note] |

## Verification (Success Criteria)
[How to prove the implementation is correct (The GREEN phase). Agent must run these checks.]
- [ ] [Verification check 1, e.g., run test suite]
- [ ] [Verification check 2, e.g., verify no lint errors]

## Common Mistakes & Red Flags
[List specific rationalizations, shortcuts, or misunderstandings the agent might have. Address the "RED" phase baseline failures here.]

| Red Flag (Excuse / Mistake) | Reality / Fix (What to do instead) |
|-----------------------------|------------------------------------|
| "I'll just skip testing this time." | **STOP.** You must verify the behavior first. |
| [Mistake or excuse]         | **STOP.** [Correct action]         |
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall