Agent skill · writing content · github
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) 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.
Why this skill is useful
Adds a structured workflow for creating and updating personal context portfolios that the AI wouldn't reliably generate on its own.
What it needs
About 13k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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-path> (or equivalent path reference) anywhere in the loaded instruction text. That's the file's location. Don't rely on the label or variable name next to the path: users may name pointers differently (identityProfile, me, who-i-am, etc.). Match on the filename at the end of the path. For each filename, classify as: NOT REFERENCED — no path to this filename is loaded in the session. REFERENCED, FILE MISSING — a path is loaded but the file doesn't exist on disk. PRESENT — path is loaded and the file exists. Read it to check for placeholders. If the six filenames are in mixed states, handle them in this priority order: first create any NOT REFERENCED files via the interview, then fill REFERENCED, FILE MISSING entries, then fix incomplete fields in PRESENT files. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/setup-my-iq