/ijfw-status
Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner.
$ npx -y skills add FerroxLabs/ijfw --skill ijfw-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ijfw-status
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner.
SKILL.md
ijfw-status.SKILL.mdname: ijfw-status
description: "Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner."
IJFW Status
Report the following in order. Use positive framing throughout -- no negatives, no "not found".
1. Session Mode
Read `.ijfw/config.json` if present. Report current mode: Quick / Deep / default. If no config, report "running on smart defaults".
2. Memory Tiers
- **Working memory**: check `.ijfw/.prompt-check-state` -- report "active" if present, "clean slate" if not.
- **Project memory**: list files in `.ijfw/memory/` -- report count and most recent handoff date. If empty, "ready for first capture".
- Do NOT report global/warm tiers unless explicitly asked.
3. Hook Status
Check `.ijfw/.prompt-check-state` for `"fired": true`. Report: "Prompt sharpener active" or "Prompt sharpener standing by".
4. MCP Server
Call `ijfw_metrics`. Report its output as a single line. If the tool is unreachable, report "Memory server standing by -- run `claude mcp add` to connect".
5. Last Handoff
Read `.ijfw/memory/` for the most recent `HANDOFF*.md` or `handoff*.md`. Extract the date and first heading. Report as: "Last session: <date> -- <heading>". If none, "No handoff yet -- first session captures automatically".
Format
Emit as a compact table or 5-line list. No headers larger than `##`. End with one receipt line:
> `IJFW active -- <N> memory entries, <mode> mode, hooks live.`
Total output: under 20 lines. Positive framing only.
Read more
name: ijfw-status description: "Use when the user says: 'ijfw status', 'show me the system state', 'what is ijfw doing', or to see the at-a-glance routing / memory / activity banner."
IJFW Status
Report the following in order. Use positive framing throughout -- no negatives, no "not found".
1. Session Mode
Read `.ijfw/config.json` if present. Report current mode: Quick / Deep / default. If no config, report "running on smart defaults".
2. Memory Tiers
- **Working memory**: check `.ijfw/.prompt-check-state` -- report "active" if present, "clean slate" if not.
- **Project memory**: list files in `.ijfw/memory/` -- report count and most recent handoff date. If empty, "ready for first capture".
- Do NOT report global/warm tiers unless explicitly asked.
3. Hook Status
Check `.ijfw/.prompt-check-state` for `"fired": true`. Report: "Prompt sharpener active" or "Prompt sharpener standing by".
4. MCP Server
Call `ijfw_metrics`. Report its output as a single line. If the tool is unreachable, report "Memory server standing by -- run `claude mcp add` to connect".
5. Last Handoff
Read `.ijfw/memory/` for the most recent `HANDOFF*.md` or `handoff*.md`. Extract the date and first heading. Report as: "Last session: <date> -- <heading>". If none, "No handoff yet -- first session captures automatically".
Format
Emit as a compact table or 5-line list. No headers larger than `##`. End with one receipt line:
> `IJFW active -- <N> memory entries, <mode> mode, hooks live.`
Total output: under 20 lines. Positive framing only.
IJFW — It Just F*cking Works. Ferrox Labs' local-first infrastructure for AI coding agents: shared memory, smart routing, multi-AI cross-audits, disciplined workflow.
Repo: FerroxLabs/ijfw
Other skills on ijfw.
- /ijfw-agents-md
Maintain canonical AGENTS.md (open spec). Trigger: 'agents.md', 'update AGENTS.md', or auto-fired by ijfw-team after agent generation.
Open skill - /ijfw-auto-memorize
Session-end auto-extraction of lessons, errors, fixes, and user feedback into structured memory. Fires at session end. Requires consent on first run.
Open skill - /ijfw-commit
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit
Open skill - /ijfw-complete-milestone
Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship milestone', 'wrap milestone', 'complete milestone <id>', /ijfw-complete-milestone.
Open skill - /ijfw-compress
Compress memory/context files into terse form. Trigger: /compress, compress file
Open skill - /ijfw-compute
Use when the user says: 'compute', 'crunch this', 'analyze logs', 'aggregate the data', 'run a script', 'dedupe', 'count by', 'top N', or any data-shaping ask. Replaces dumping raw data into context with sandboxed script execution.
Open skill