From consider
Scope decisions by distinguishing what you know well from what you don't
How this skill is triggered — by the user, by Claude, or both
Slash command
/consider:circle-of-competenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<objective>
<output_format>
[The decision or area being evaluated]
[Which zones does this decision touch?]
[Stay inside / expand the circle / bring in outside expertise] </output_format>
## Circle of Competence: Should Our Backend Team Build the Mobile App?Deciding whether our team of 3 backend engineers should build the iOS/Android app ourselves or hire specialists.
Building the mobile app requires deep knowledge in all three zones. API integration is inside our circle, but the entire frontend layer — UI, platform APIs, store submission — is outside it.
Bring in outside expertise. Hire or contract a mobile developer for the app shell and platform integration. Our team owns the API layer and backend (inside our circle). The mobile specialist handles what we'd spend months learning poorly. Review architecture decisions together so knowledge transfers over time.
npx claudepluginhub bcbeidel/toolkit --plugin considerPrevents confident fabrications by grounding answers in verifiable evidence. Abstains, asks, or fetches when uncertain rather than confabulating.
Provides radically candid coaching as a thinking partner for strategic situations, clarifying stakes, building domain expertise, and strengthening decisions.
Extracts and structures tacit knowledge from digital product domains like UI/UX, marketing, and growth into reusable agent definitions and evaluation criteria. Use to build best practices or expert evaluation standards.