setup-my-iq
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
Profile →npx skills add github/awesome-copilot --skill setup-my-iq --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Create and maintain the personal context portfolio: a set of structured markdown files that represent who you are, how you work, and what matters to you. The files can live anywhere on disk. Trigger this skill when the user asks to set up their context, create or update their context portfolio, or related phrases, and when another skill fails to find context.
How it works
- Discover existing context by scanning for six target files: identity.md, role-and-responsibilities.md, team.md, tools-systems-and-config.md, communication-style.md, and preferences-and-constraints.md. Identify whether each is NOT REFERENCED, REFERENCED, FILE MISSING, or PRESENT.
- If NOT REFERENCED: proceed with First-Time Setup interviews to create files.
- If some files are REFERENCED or PRESENT: resume where left off, prioritizing creation first, then filling gaps, then fixing incomplete fields.
- For each file, load the corresponding template from assets/templates/* and run an interview workflow to populate fields. Pre-fill from available data sources when possible, then ask targeted questions to fill remaining fields.
- During interviews, handle identity, role-and-responsibilities, team, tools-systems-and-config, and communication-style in sequence, building a cohesive context portfolio.
- After drafting, present findings, revise with user feedback, and write to the context directory.
When to use it
Trigger when the user asks to set up their context, create or update their context portfolio, or related phrases like "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. Also trigger if another skill fails to find context (missing files or TODO markers).
What it can touch
- Uses the host's templates located under assets/templates for each file type.
- Interacts with the session-embedded references to identify file paths like identity.md, role-and-responsibilities.md, team.md, tools-systems-and-config.md, communication-style.md, preferences-and-constraints.md.
Caveats
- Mandates a first-time interview flow and targeted edits for updates; may create or modify files based on user input.
- Pre-fill is conditional on available data sources; if no sources are accessible, the skill proceeds with direct questioning.
- Avoids triggering on read-only questions about existing context; those are answered directly from loaded context files without invoking this skill.
# Setup My IQ: Create and Update Context Portfolio Create and maintain the personal context portfolio: a set of structured markdown files that represent who you are, how you work, and what matters to you. The files can live anywhere on disk (OneDrive folder, a git repo, a local directory, etc.). What ties them into the agent is a pointer in one of the user's custom instructions files (`AGENTS.md`, `copilot-instructions.md`, `CLAUDE.md`, or any `*.instructions.md` that the host loads into the session). ## How This Skill Works When invoked, determine the current state and take the right action. ### Discovering existing context Scan the session for references to the files this skill creates. The host has already merged all relevant custom instructions files into the session: `AGENTS.md` (workspace or user-scope), `copilot-instructions.md`, `CLAUDE.md`, any `*.instructions.md` file, and similar host-specific equivalents. It doesn't matter which file the pointer came from, just look for the filenames: - `identity.md` - `role-and-responsibilities.md` - `team.md` - `tools-systems-and-config.md` - `communication-style.md` - `preferences-and-constraints.md` For each, find an `@<absolute-pat
- How This Skill Works
- Discovering existing context
- 1. No context files referenced
- 2. Some files referenced but missing on disk
- 3. Files exist but have incomplete fields
- 4. Files are complete, user wants to update
- 5. Files are complete, user wants a full refresh
- First-Time Setup
- 1. Choose context directory
- 2. Begin the interview
- 3. Pre-fill factual fields from available data sources
- 4. Interview for identity.md
- 5. Interview for role-and-responsibilities.md
- 6. Interview for team.md
What does the setup-my-iq skill do?
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
How do I install it?
Run `npx skills add github/awesome-copilot --skill setup-my-iq --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 github/awesome-copilot, a repository with 37,432 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.