Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From workiq
Use this skill proactively during coding workflows that involve people, teams, or organizational context. Triggers include git blame output with email addresses, PR reviews, code ownership questions, finding design docs referenced in code, understanding decisions behind code changes, encountering person names in comments or documentation, onboarding to unfamiliar repos, and any mention of "who is", "who owns", "who works on", "what team", meetings, emails, or Teams channels.
npx claudepluginhub aanerud/claude-code-workiq-plugin --plugin workiqHow this skill is triggered — by the user, by Claude, or both
Slash command
/workiq:workiq-capabilitiesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Work IQ connects Claude Code to the user's Microsoft 365 environment via MCP. It answers natural language queries about people, emails, meetings, documents, and Teams messages.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Guides systematic root-cause debugging when tests fail, builds break, or unexpected errors occur. Provides a structured triage checklist to preserve evidence, localize, and fix issues instead of guessing.
Share bugs, ideas, or general feedback.
Work IQ connects Claude Code to the user's Microsoft 365 environment via MCP. It answers natural language queries about people, emails, meetings, documents, and Teams messages.
When you run git blame or git log and see email addresses or author names:
| Trigger | Query |
|---|---|
See johndoe@company.com in git blame | "Who is johndoe@company.com? What team are they on?" |
| See unfamiliar author in git log | "What is the role of Jane Smith?" |
| Multiple authors on a file | "Who is the manager of johndoe@company.com?" to find the team lead |
When reviewing or creating PRs:
| Trigger | Query |
|---|---|
| Reviewing a PR from an unfamiliar author | "Who is sarah@company.com and what team are they on?" |
| PR references a project or initiative | "Find design documents for Project Phoenix" |
| PR implements a decision you need context on | "What was discussed in the architecture review meeting about caching?" |
When the user needs to know who owns, maintains, or is responsible for code:
| Trigger | Query |
|---|---|
| "Who owns this service?" | "Who is the lead developer on the auth-service?" |
| Need to escalate or get approval | "Who is the manager of the payments team?" |
| Looking for a subject matter expert | "Who is working on the database migration project?" |
When code comments, commit messages, or PRs reference decisions but don't explain them:
| Trigger | Query |
|---|---|
| Comment says "per arch review decision" | "What was decided in the architecture review about the API gateway?" |
| Commit message references a project | "Find emails about Project Atlas from last month" |
| Code has a workaround with no explanation | "What was discussed in the Backend Engineering channel about rate limiting?" |
When a user is new to a codebase and needs organizational context:
| Trigger | Query |
|---|---|
| User says "I'm new to this repo" | "Who is the lead developer on [service name]?" |
| README references a team or project | "What team owns the notification service?" |
| Need to find specs or architecture docs | "Find design documents for the user authentication system" |
When code references documents, RFCs, or specs:
| Trigger | Query |
|---|---|
| Code comment says "see design doc" | "Find design documents for [feature name]" |
| Need API specs or requirements | "Find the specification document for the REST API v2" |
| Looking for test plans or runbooks | "Find documents about deployment runbook for payments" |
When work involves scheduled events:
| Trigger | Query |
|---|---|
| User is preparing for a review | "What meetings do I have about the API migration?" |
| Need context from a past meeting | "Summarize the standup transcript from yesterday" |
When the user needs communication context:
| Trigger | Query |
|---|---|
| Looking for context on a decision | "What emails were sent about the database schema change?" |
| Need to check team discussions | "What has been discussed in the Platform Engineering channel about caching?" |
Use the Work IQ MCP tools directly. The tool accepts a single natural language question — keep queries specific and include names, email addresses, or project names when available.
Good queries:
Avoid:
Work IQ requires:
If Work IQ is not set up, direct the user to /workiq:setup.