Skip to content
Back to skills

Response Format Lovedragonball Power Ranger Toolkit 2

ASecurity

Ensure all AI responses are well-formatted, easy to understand, and actionable

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsjavascriptgojavagitdocumentation

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill response-format-lovedragonball-power-ranger-toolkit-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Response Format Lovedragonball Power Ranger Toolkit 2?

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

Security grade badge for Response Format Lovedragonball Power Ranger Toolkit 2
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-response-format-lovedragonball-power-ranger-toolki/badge)](https://www.skillsdirectory.com/skills/majiayu000-response-format-lovedragonball-power-ranger-toolki)

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: response-format
description: Ensure all AI responses are well-formatted, easy to understand, and actionable
  for the user.
---

# πŸ“ Response Format Skill

---
name: response-format
description: Format AI responses for clarity, readability, and actionability
---

## 🎯 Purpose

Ensure all AI responses are well-formatted, easy to understand, and actionable for the user.

## πŸ“‹ When to Use

- Every response to user
- Documentation generation
- Report creation
- Summary generation

## πŸ”§ Formatting Guidelines

### Headers
```markdown
# H1 - Main Topic (use sparingly)
## H2 - Sections
### H3 - Subsections
#### H4 - Details (rarely needed)
```

### Lists
```markdown
**Bullet Lists** - For unordered items:
- Item 1
- Item 2
  - Sub-item

**Numbered Lists** - For sequences:
1. First step
2. Second step
3. Third step
```

### Code Blocks
````markdown
**Inline code**: Use `backticks` for code

**Code block with language**:
```javascript
const example = "highlighted";
```
````

### Tables
```markdown
| Column 1 | Column 2 | Column 3 |
|----------|----------|----------|
| Data 1   | Data 2   | Data 3   |
```

## πŸ“Š Response Templates

### Summary Response
```markdown
## πŸ“‹ Summary

**Goal**: [What we're doing]

**Key Points**:
- Point 1
- Point 2
- Point 3

**Next Steps**:
1. [Action 1]
2. [Action 2]
```

### Technical Explanation
```markdown
## πŸ”§ [Topic]

### What
[Brief explanation]

### Why
[Reasoning]

### How
```code
[Implementation]
```

### Example
[Usage example]
```

### Problem/Solution
```markdown
## πŸ› Problem

[Description of issue]

## βœ… Solution

[How to fix]

## πŸ’‘ Prevention

[How to avoid in future]
```

## 🎨 Visual Enhancements

### Emoji Usage
| Category | Emojis |
|----------|--------|
| Success | βœ… πŸŽ‰ 🟒 |
| Warning | ⚠️ 🟑 |
| Error | ❌ πŸ”΄ πŸ› |
| Info | ℹ️ πŸ’‘ πŸ“‹ |
| Tasks | πŸ“‹ ✏️ πŸ”§ |

### Emphasis
```markdown
**Bold** - Important terms
*Italic* - Subtle emphasis
`Code` - Technical terms
> Quote - Callouts
```

### Alerts (GitHub style)
```markdown
> [!NOTE]
> Helpful information

> [!TIP]
> Optimization suggestion

> [!IMPORTANT]
> Critical information

> [!WARNING]
> Potential issues

> [!CAUTION]
> Dangerous actions
```

## πŸ“ Response Length Guidelines

| Type | Length | Example |
|------|--------|---------|
| Quick answer | 1-3 sentences | Yes/No questions |
| Explanation | 1-2 paragraphs | How-to questions |
| Tutorial | Multiple sections | Step-by-step guides |
| Report | Full document | Analysis, summaries |

## βœ… Response Checklist

- [ ] Clear structure with headers
- [ ] Scannable (bullets, tables)
- [ ] Code properly formatted
- [ ] Actionable next steps
- [ ] Appropriate length
- [ ] Emoji for visual clarity

## πŸ”— Related Skills

- `documentation` - Full docs
- `progress-tracking` - Progress reports
- `business-context` - Business reports

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.