clarifying-scenarios Skill
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via Published by microsoft in github-copilot-modernization.
What is clarifying-scenarios Skill?
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via Published by microsoft in github-copilot-modernization. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Data analysis
- Design and media
- Writing
- Data analysis use cases
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use clarifying-scenarios Skill
- Use it for data analysis.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/github-copilot-modernization
- Skill file: plugins/github-copilot-modernization/skills/clarifying-scenarios/SKILL.md
What it does
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, asks the user for missing required fields via
Skill instructions
Purpose Frontend rewrites in particular fail silently when the user prompt omits the target component library, screenshots, or compliance requirements. This skill catches those gaps before decomposition by: 1. Evaluating the raw user prompt + project facts against three kits (frontend, backend, generic). 2. Computing a deterministic clarity score. 3. Asking the user — exactly once per round, in a single batched form — for missing required/recommended fields. 4. Writing a canonical clarification.md consumed by Foundation/Design/Plan agents. Inputs You receive these from the coordinator (via task metadata or dependencyArtifacts): | Input | Source | Required | |-------|--------|----------| | userInput (raw user prompt) | task metadata | yes | | classification (type, complexity, target, etc.) | coordinator §1 output | yes | | projectfacts (detected tech stack, frontend/backend presence) | coordinator §2.1 output | yes | | interactive (boolean — is a TTY available?) | session env (default t
Explore related resources
Frequently asked questions
What is clarifying-scenarios?
clarifying-scenarios is a open-source AI agent skill with Copy skill directory. Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy.
Who is clarifying-scenarios best for?
clarifying-scenarios is best for reusing agent instructions, scripts, and references, data analysis workflows, design and media workflows, writing workflows.
How do I install clarifying-scenarios?
Install or run clarifying-scenarios using Copy skill directory. Check clarifying-scenarios for the latest setup command.
Is clarifying-scenarios actively maintained?
clarifying-scenarios may need a closer maintenance check before production use.
Auto-fetched from GitHub.
