ijfw-doctor
Diagnose IJFW integration health per platform. Trigger: 'doctor', 'check setup', /doctor
pinned to #eda62f3updated 2 months ago
Ask your AI client: “install skills/ijfw-doctor”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/ijfw-doctormetahub onboarded this repo on the author's behalf.
If you own github.com/FerroxLabs/ijfw on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
197
Last commit
2 months ago
Latest release
published
- #ai-agents
- #ai-coding
- #claude-code
- #codex
- #cursor
- #developer-tools
- #gemini-cli
- #github-copilot
- #mcp
- #mcp-server
- #memory
- #nodejs
- #typescript
- #windsurf
About this skill
Pulled from SKILL.md at publish time.
Run each check silently, then emit a single positive-framed report. Never say "failed", "error", or "not found" -- reframe every finding as an action or a ready state.
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.eda62f3· 2 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
11 words · 88 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
18,480 chars · 6 sections · 4 code blocks
Tags / topics declared
14 total — ai-agents, ai-coding, claude-code, codex, cursor, developer-tools (+8)
README has usage / example sections
found: Quickstart
Homepage / docs URL declared
https://www.npmjs.com/package/@ijfw/install
Release history
1- releasecurrenteda62f3warn2 months ago
Contents
Run each check silently, then emit a single positive-framed report. Never say "failed", "error", or "not found" -- reframe every finding as an action or a ready state.
Checks (run in order)
1. MCP Server
Call ijfw_metrics. If it responds: "Memory server active". If unreachable: "Memory server ready to connect -- run claude mcp add ijfw-memory node /path/to/mcp-server/src/index.js".
2. Memory Directory
Check .ijfw/memory/ exists and is writable (test -w .ijfw/memory). If writable: "Memory directory writable". If missing: "Memory directory ready to create -- first memory write will initialize it".
3. Hooks
Check for hook scripts in the platform's hooks directory (e.g. ~/.claude/hooks/ for Claude, .codex/hooks/ for Codex). If scripts exist and are executable: "Hooks registered and live". If missing: "Hooks standing by -- re-run install.sh to register".
4. Platform Integration Depth
Report which features are active based on what's detected:
- MCP connected = deep integration
- Hooks present = prompt sharpener active
- Memory populated = context carry-over active
- Config present = custom rules loaded
5. Node.js Version
Run node --version. If 18+: "Runtime ready (Node <version>)". If missing or older: "Node.js 18+ needed -- install from https://nodejs.org".
Format
5-line list, one line per check, all positive. End with:
All systems active -- IJFW running at full depth.
Or if any items need action:
IJFW active -- <N> of 5 systems at full depth. Steps above complete the setup.
Under 20 lines total. No negatives.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/ijfw-doctor