descriptive-action
Use when the user asks to describe, summarize, analyze, compare, explain, or report on something (text, data, events, systems) without asking for recommendations or next steps.
When & Why to Use This Skill
The Descriptive Action skill is a specialized tool designed to provide objective, high-fidelity analysis and structured descriptions of complex information. It excels at distilling text, data, and systems into neutral summaries and factual reports without the interference of unsolicited recommendations. By strictly separating facts from inferences and focusing on structured outputs, this skill ensures that users receive clear, unbiased insights that serve as a reliable foundation for informed decision-making.
Use Cases
- Executive Summarization: Transforming lengthy documents, meeting transcripts, or research papers into concise, bulleted summaries that capture essential points and background information.
- Comparative System Analysis: Providing a neutral side-by-side comparison of different technical systems, software architectures, or datasets to identify functional differences and commonalities.
- Data Fact Extraction: Scanning raw data or reports to extract specific metrics, observations, and trends, presenting them in a structured format for status reporting.
- Technical Explanations: Breaking down complex concepts or system behaviors into clear, structured descriptions for documentation or educational purposes without prescribing specific actions.
| name | descriptive-action |
|---|---|
| description | Use when the user asks to describe, summarize, analyze, compare, explain, or report on something (text, data, events, systems) without asking for recommendations or next steps. |
| version | 1.0 |
Descriptive Action Skill
Purpose
Produce accurate, neutral descriptions and analyses. Do not prescribe actions unless explicitly requested.
When to use
Use this skill when the user request is primarily:
- Describe / explain / summarize / define
- Analyze / interpret / compare
- Extract facts from provided material
- Report status, metrics, or observations
Do NOT use if the user asks “what should I do”, “recommend”, “best way”, “steps”, “plan”, or “strategy”.
Operating rules
- Stay observational: focus on what is true in the input and what can be inferred safely.
- Separate facts from interpretation:
- Facts: directly supported by the provided input.
- Inferences: clearly labeled.
- If key information is missing, state what’s missing and proceed with bounded analysis.
- Avoid normative language.
- Prefer structure over prose.
Inputs
- Text, data, artifacts, or systems to describe
- Any stated constraints (scope, timeframe, audience)
Outputs
Structured descriptive analysis using the format below.
Summary
- 3–6 bullets capturing the main points.
Details
- Organized sections (background, findings, trends, constraints).
Evidence
- Brief references to supporting input.
Open questions
- Unknowns limiting confidence.