# Describe Information With Neutral Analysis

Descriptive requests can drift into advice, plans, or unsupported conclusions. This skill keeps responses factual, structured, and clearly separated between evidence and inference.

## Install

```bash
npx skillstore add bellabe/descriptive-action
```

## Metadata

- - Slug: bellabe-descriptive-action
- - Version: 1.0
- - Author: BellaBe
- - GitHub username: BellaBe
- - License: MIT
- - Repository: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/action-descriptive
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Quality score: 79
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/bellabe-descriptive-action
- - Manifest: https://skillstore.pages.dev/api/skills/bellabe-descriptive-action/manifest

## Capabilities

- Summarizes provided text, data, events, systems, or artifacts.
- Explains concepts and observations without giving recommendations.
- Separates directly supported facts from labeled inferences.
- Compares inputs using neutral, structured sections.
- Reports missing information and open questions that limit confidence.

## Use Cases

- Summarize Meeting Notes: Turn long notes into neutral summaries with facts, themes, and open questions.
- Compare Product Feedback: Describe similarities, differences, patterns, and constraints across user comments.
- Explain Technical Material: Convert dense documentation or system descriptions into clear, bounded explanations.

## Prompt Templates

### Basic Summary

```
Summarize the following material. Separate facts from inferences and list any open questions.
```

### Structured Explanation

```
Explain this material using sections for summary, details, evidence, and unknowns. Avoid recommendations.
```

### Neutral Comparison

```
Compare these items by describing shared traits, differences, evidence, and confidence limits. Do not choose a winner.
```

### Evidence-Bounded Analysis

```
Analyze the provided material. Label facts, interpretations, trends, constraints, and missing information. Keep conclusions bounded by evidence.
```

## Limitations

- Does not provide recommendations unless the user explicitly asks for them.
- Does not create step-by-step plans or strategies for action requests.
- Depends on the quality and completeness of the supplied material.
- Does not verify external facts unless another tool or source is available.

## Best Practices

- Provide the source material and define the desired scope before asking for analysis.
- Ask for facts, inferences, evidence, and open questions when accuracy matters.
- State the audience so the explanation uses the right level of detail.

## Anti Patterns

- Do not use this skill when you need recommendations or a decision.
- Do not ask it to invent facts that are missing from the input.
- Do not mix descriptive analysis with action planning in the same request.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T14:42:18.109\+00:00
- - Summary: Static analysis reported weak cryptographic algorithm and system reconnaissance patterns, but review found only ordinary documentation text in SKILL.md. No executable code, cryptography, command execution, network access, filesystem access, prompt injection, or data exfiltration behavior was found. The static findings are false positives and the skill is safe to publish.

## Stats

- - Views: 158
- - Downloads: 5
- - Favorites: 0
- - Popularity score: 0