Descriptive action
Skill ComeOnOliver/skillshub/skills/aiskillstore/marketplace/bellabe/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.From its SKILL.md
npx -y skills add ComeOnOliver/skillshub --skill descriptive-actionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.5 KB, 274 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it
8.1 KB alongside SKILL.md
GitHub clipped this repository’s file list, so this is at least 1 file and may be more.
- skill-report.json8.1 KB