Skip to content
Back to skills

Small To Before Research

ASecurity

Transform vague or informal prompts into structured, precise prompts optimized for the researchCodebase agent. Use when preparing to launch codebase research and the user's request needs refinement for better results.

  • 34 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 7, 2026
developmentdebuggingdocumentation

Security analysis

A100/100

Scanned February 10, 2026

npx -y skills add oxedom/haflow --skill small-to-before-research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Small To Before Research?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Small To Before Research
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/oxedom-small-to-before-research/badge)](https://www.skillsdirectory.com/skills/oxedom-small-to-before-research)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: small-to-before-research
description: Transform vague or informal prompts into structured, precise prompts optimized for the researchCodebase agent. Use when preparing to launch codebase research and the user's request needs refinement for better results.
---

# Small to Before Research

Transform vague prompts into optimized research prompts for the researchCodebase agent.

## Process

1. **Analyze the vague input** - Identify the core intent, implicit assumptions, and missing specifics
2. **Extract key elements**:
   - What is being searched for (files, patterns, implementations, architecture)
   - Why (understanding, modification, debugging, documentation)
   - Scope constraints (specific directories, file types, modules)
3. **Generate optimized prompt** with these characteristics:
   - Imperative voice ("Find...", "Identify...", "Document...")
   - Specific search targets (function names, patterns, file types)
   - Clear deliverables (list files, explain flow, map dependencies)
   - Scope boundaries when applicable

## Output Format

```
**Research Prompt:**

[Optimized prompt here]

**Search Targets:**
- [Specific files/patterns/keywords to look for]

**Expected Deliverables:**
- [What the research should produce]
```

## Examples

**Vague:** "how does auth work"
**Optimized:**
```
Research Prompt:
Document the authentication flow from login to session management. Identify entry points, middleware, token handling, and session storage mechanisms.

Search Targets:
- auth, login, session, token, middleware, jwt, passport
- Files: *auth*, *session*, *login*

Expected Deliverables:
- Authentication entry points and routes
- Token/session lifecycle
- Key files and their relationships
```

**Vague:** "find where we handle errors"
**Optimized:**
```
Research Prompt:
Locate error handling patterns across the codebase. Document centralized error handlers, try-catch patterns, error middleware, and custom error classes.

Search Targets:
- error, catch, throw, ErrorHandler, middleware
- Files: *error*, *exception*, *handler*

Expected Deliverables:
- Error handling entry points
- Custom error classes/types
- Error propagation patterns
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…