This skill should be used when the user says "start research", "run the research lanes", "initialize the QMi research engine", "what lanes are running", "run lane [N]", "research [topic]", "add notes on [domain]", "run a research session", "check research status", "what have we researched so far", "how many notes do we have", or any request to generate, collect, or review knowledge base notes on a domain. Also triggers on "set up the research engine" or "initialize this machine for research" when run for the first time.
npx claudepluginhub vertix-solutions/qmi-security-innovations --plugin qmi-security-innovationsThis skill uses the workspace's default tool permissions.
This machine runs as an auxiliary research engine for the QMi Security Innovations knowledge base. There are 8 active research lanes, each targeting a specific IT/sysadmin domain. Each lane runs independently and produces structured research notes that can be packaged and transferred to the primary Vertix Solutions machine.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
This machine runs as an auxiliary research engine for the QMi Security Innovations knowledge base. There are 8 active research lanes, each targeting a specific IT/sysadmin domain. Each lane runs independently and produces structured research notes that can be packaged and transferred to the primary Vertix Solutions machine.
These are the 8 active lanes. Treat this as the source of truth unless overridden by an incoming manifest (see receive-manifest skill).
| Lane | Domain Slug | Display Name | Target Notes | Schedule |
|---|---|---|---|---|
| L1 | microsoft-365-administration | Microsoft 365 Administration | 60 | XX:00 |
| L2 | entra-id-identity-management | Entra ID / Azure AD | 60 | XX:08 |
| L3 | itsm-frameworks-itil | ITSM Frameworks — ITIL v4 | 60 | XX:16 |
| L4 | hubspot-crm-administration | HubSpot CRM Administration | 60 | XX:24 |
| L5 | netsuite-erp-operations | NetSuite ERP Operations | 60 | XX:32 |
| L6 | powershell-windows-automation | PowerShell & Windows Automation | 60 | XX:40 |
| L7 | microsoft-graph-api | Microsoft Graph API | 60 | XX:48 |
| L8 | it-helpdesk-operations | IT Help Desk Operations | 50 | XX:56 |
All research output goes into:
qmi-kb/
[domain-slug]/
[domain-slug]-notes-001.md
[domain-slug]-notes-002.md
...
Every note file must include this frontmatter:
---
domain: [exact domain slug from lane registry]
source: qmi-machine
date: [YYYY-MM-DD]
notes_in_batch: [integer — count of discrete notes in this file]
research_session: [short session identifier]
---
Each note is a discrete, self-contained research finding — 3 to 8 sentences. Number notes sequentially within the file. Aim for 10–15 notes per file before creating a new one.
When asked to run a lane or research a domain:
qmi-kb/[domain-slug]/ to determine current note count and avoid duplicationqmi-kb/[domain-slug]/[domain-slug]-notes-[NNN].md with correct frontmatterWhen asked for research status, scan qmi-kb/ and report:
QMi Research Engine — Status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Lane Domain Notes Target Gap Status
L1 microsoft-365-administration [N] 60 [N] [🟢/🟡/🔴]
L2 entra-id-identity-management [N] 60 [N] [🟢/🟡/🔴]
...
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total notes: [N] / [total target]
Recommended next lane: [lane with largest gap or lowest % complete]
Status key: 🟢 = target met | 🟡 = 15–59 notes | 🔴 = 0–14 notes
If qmi-kb/ does not exist, create it with one subfolder per lane slug. Confirm setup is complete and prompt the user to run their first lane.
See references/domain-scopes.md for the full research scope brief for each domain.