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.
Best use case
descriptive-action is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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.
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.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "descriptive-action" skill to help with this workflow task. Context: 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.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/descriptive-action/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How descriptive-action Compares
| Feature / Agent | descriptive-action | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 1. Stay observational: focus on what is true in the input and what can be inferred safely. 2. Separate facts from interpretation: - Facts: directly supported by the provided input. - Inferences: clearly labeled. 3. If key information is missing, state what’s missing and proceed with bounded analysis. 4. Avoid normative language. 5. 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.
Related Skills
github-actions-docs
Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.
interaction-design
Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, or creating delightful user experiences.
security-requirement-extraction
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
control-loop-extraction
Extract and analyze agent reasoning loops, step functions, and termination conditions. Use when needing to (1) understand how an agent framework implements reasoning (ReAct, Plan-and-Solve, Reflection, etc.), (2) locate the core decision-making logic, (3) analyze loop mechanics and termination conditions, (4) document the step-by-step execution flow of an agent, or (5) compare reasoning patterns across frameworks.
star-story-extraction
Auto-invoke after task completion to extract interview-ready STAR stories from completed work.
resume-bullet-extraction
Auto-invoke after task completion to generate powerful resume bullet points from completed work.
design-spec-extraction
Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.
standards-extraction
Extract coding standards and conventions from CONTRIBUTING.md, .editorconfig, linter configs. Use for onboarding and ensuring consistent contributions.
prescriptive-actions
Use when the user asks for recommendations, next steps, best approaches, or “what should I do” guidance to achieve a goal or fix a problem.
planning-action
Use when the user asks for a roadmap, timeline, phased plan, or execution sequence.
diagnostic-action
Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.