SkillsAdd

smithery/ezej

modality-scope

Use RFC-2119 modality (SHALL/SHOULD/MAY) only in true requirement Statements, not in summaries/analysis/notes. Use when strict modality is distorting meaning (e.g., interview summaries, early discovery) or making outputs harder to read.

Installation

$ npx skills add smithery/ezej --skill modality-scope
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery/ezej.

npx skills add smithery/ezej
stage-and-risk-selection 0

Browse all from smithery/ezej

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 824 B
  • docs SUMMARY.md 258 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Modality Scope

Rules

  1. Decide where modality is required:

- Requirements: use SHALL/SHOULD/MAY. - Everything else (summaries, rationale, notes, conflicts, options): use plain language unless there is a strong reason not to.

  1. Don’t force modality onto stakeholder voice:

- Keep direct quotes and summaries in natural language.

Prompt snippet (copy/paste)

Use RFC-2119 modality (SHALL/SHOULD/MAY) ONLY in the Requirement Statement field.
In summaries/rationale/notes, use plain language for clarity.