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.
NewMaintained
Automatic
◆Research pack
Last verified 9/3/2026
What it changes
Passed 12 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill55%
Checks it passed that the model alone missed
The response omits prescriptive action recommendations.
The response includes a summary section with bullet points.
The response lists missing payload details as open questions.
and 4 more in the full report
3 fixed9 passed either way7 still failing3 broke
Pass-rate lift
0 pp
Tokens
+20%
Agent turns
0%
Response time
+4%
Model gemini-3.6-flashMeasured 9/3/2026v112 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
Here is our quarterly infrastructure performance log and downtime reports from last month. Please analyze this data and give me an objective, structured breakdown of the facts, key findings, and remaining unknowns. Just describe what happened and what the metrics show—do not give recommendations or tell us what steps to take next.
What was checked, without and with the skill
Checked
Without skill
With skill
The response includes a summary section with bullet points.
Missed
Passed
The response explicitly identifies missing inputs limiting confidence.
Missed
Passed
The response omits prescriptive action recommendations.
Missed
Passed
case-01 · gemini-3.6-flash · 9/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md41 linessingle file
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.
Use this skill when creating or evolving design systems for applications. Provides design token structures, component architecture patterns, documentation templates, and accessibility guidelines. Ensures consistent, scalable, and accessible UI design across products.