Skip to content

github/awesome-copilot / skills/setup-my-iq

setup-my-iq

Unverified

Create, set up, or update the personal context portfolio: structured markdown files describing who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview workflow for first-time setup and targeted edits for updates. Trigger this skill when the user asks to: set up their context, create or update their context portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder, update ADO config, change team info, update pillars, or set up any plugin configuration. Trigger when another skill fails to find context (missing files or TODO markers) and needs context populated. Also trigger when the user mentions a context change in passing (e.g., "my manager changed", "we added someone to the team") to offer a context file update. Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?". Those are answered directly from the context files referenced in the loaded custom instructions; no skill is needed.

assets/templates/communication-style.md

View on GitHub
# Communication Style

## Baseline Voice

<!-- The bullets below describe how you naturally write. Replace the placeholders with your own traits. 5 to 10 bullets is plenty. Use the format "Trait. One-line explanation." -->

- **<!-- trait, e.g., Direct and conversational -->** <!-- explanation, e.g., I write how I'd actually talk to someone. -->
- **<!-- trait, e.g., Specific over abstract -->** <!-- explanation -->
- **<!-- trait, e.g., Honest but kind -->** <!-- explanation -->
- **<!-- trait, e.g., No superlatives -->** <!-- words to avoid + words you prefer -->
- **<!-- trait -->** <!-- explanation -->

## Words and Phrases to Avoid

<!-- Specific words, patterns, or constructions that don't sound like you. AI tends to use these, so call them out explicitly. -->

- <!-- e.g., No em dashes. Use periods or commas instead. -->
- <!-- e.g., Corporate abstraction like "generated energy for others" or "broke down silos". -->
- <!-- e.g., Superlatives like "outstanding," "incredible," "genuine force multiplier". -->

## Status Updates and Reports

<!-- How you write sprint updates, weekly status, Loop updates, etc. Include rules about tense, precision, framing, and connecting work to outcomes. -->

- <!-- e.g., Use present/continuing tense for ongoing work. -->
- <!-- e.g., Don't state decisions as final unless confirmed. -->
- <!-- e.g., Frame progress with "why it matters", not just "what happened". -->
- <!-- e.g., Translate technical terms for non-technical audiences. -->

## Audience-Specific Adjustments

### Leadership

<!-- How your writing changes for your manager, skip-level, or executive audiences. Structure, scannability, level of context, anything specific to that audience. -->

### Team

<!-- How you write to your direct teammates. Tone, jargon, register. -->

### External

<!-- Cross-org partners, vendors, customers. What shifts when the audience doesn't share your background? -->

## Performance Reviews and Self-Assessment

<!-- Optional. Rules for writing about yourself in Connect, performance reviews, or peer feedback. How to talk about your own contributions without overclaiming. -->

- <!-- e.g., Lead with what changed because of the work, not just what was done. -->
- <!-- e.g., Be honest about my specific role. Don't absorb credit, don't inflate. -->
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall