resolving-skill-conflicts
Use when candidate techniques, providers, policy profiles, ownership rules, or tool effects cannot safely coexist in the same execution route.
Profile →npx skills add casioreview20-glitch/forge-os --skill resolving-skill-conflicts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Resolving Skill Conflicts ## Core principle Classify conflict as semantic, resource, authority, state, or side-effect conflict. Record excluded alternatives and invalidation consequences. The runtime owns deterministic scope, coverage, policy, and evidence checks; the agent owns only the judgment that cannot be reduced safely to code. ## Do not activate when - alternatives are compatible and can run independently - a provider is merely lower ranked without a conflict
- Core principle
- Do not activate when
What does the resolving-skill-conflicts skill do?
Use when candidate techniques, providers, policy profiles, ownership rules, or tool effects cannot safely coexist in the same execution route.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill resolving-skill-conflicts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From casioreview20-glitch/forge-os, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.