McGheeLab
Community@McGheeLab
McGheeLab builds research-management utilities for importing lab protocols, bundling manuscripts, annotating papers, and enforcing disciplined debugging and architecture reviews.
Agent Skills by McGheeLab
Showing 6 vetted skills indexed across 1 GitHub repositories.
McGheeLabarchitecture-pass
Scans one codebase subsystem with a deletion test to produce an architecture report.
McGheeLabprotocol-import
Convert lab protocol files into RM Protocols Builder import JSON with live formula blocks.
McGheeLabdiagnose
Guides structured bug diagnosis through reproduce, minimize, hypothesize, instrument, fix, and test steps.
McGheeLabpaper-bundle
Convert manuscripts and grants into validated .paperbundle.zip files for the RM Paper Builder.
McGheeLabgrill-then-plan
Interviews the user across a decision tree before writing a versioned implementation plan file.
McGheeLabpaper-overlay
Generates .paper-overlay.md files with verbatim quotes and comments for RM paper reader annotations.
Frequently Asked Questions About McGheeLab
FAQPage SchemaWhat tasks can I accomplish with McGheeLab's skills?▼
You can import .md, .docx, or .pdf lab protocols into RM Protocols Builder JSON, bundle manuscripts or grants into .paperbundle.zip files, author .paper-overlay.md annotation files for the RM paper reader, run structured debugging sequences, perform periodic architecture deletion-test scans, and conduct pre-planning interviews before drafting implementation plans.
Who are McGheeLab's skills designed for?▼
They target researchers and developers working inside the McGhee Lab RM ecosystem on mcgheelab.com — specifically users managing protocols, papers, and literature reviews across subsystems like Tasks, PMR, Paper-builder, Library, and Training, plus maintainers running periodic architecture and planning discipline.
How do I import an existing protocol or manuscript into the RM system?▼
For protocols, the skill emits a .protocol-import.json with formula blocks and base64 figures, uploaded via the Import button on protocols.html. For papers, it produces a validated .paperbundle.zip containing paper.json and assets, uploaded via the Import paper button on paper-builder.html.
When should I use the diagnose skill versus fixing a bug directly?▼
Use diagnose when a bug's root cause is unclear or spans Firestore rules, the api adapter, and the DOM — it enforces reproduce, minimize, hypothesize, instrument, fix, test. Skip it for obvious typos, missing imports, or one-line errors where the fix is already evident.
When should the architecture-pass and grill-then-plan skills be run?▼
Run architecture-pass every ~10 version bumps or before a major refactor, never per-PR or during bug fixes. Use grill-then-plan when drafting a CodeLog or version plan from a wishlist item, but skip it for trivial single-file edits, typo fixes, or already-decided refactors.