/status
Display the current state of the FPF knowledge base
$ npx -y skills add NeoLabHQ/context-engineering-kit --skill 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
/status
Context preview
The summary Claude sees to decide when to auto-load this skill.
Display the current state of the FPF knowledge base
SKILL.md
status.SKILL.mdname: status
description: "Display the current state of the FPF knowledge base"
Status Check
Display the current state of the FPF knowledge base.
Action (Run-Time)
1. **Check Directory Structure:** Verify `.fpf/` exists and contains required subdirectories. 2. **Count Hypotheses:** List files in each knowledge layer:
- `.fpf/knowledge/L0/` (Proposed)
- `.fpf/knowledge/L1/` (Verified)
- `.fpf/knowledge/L2/` (Validated)
- `.fpf/knowledge/invalid/` (Rejected)
3. **Check Evidence Freshness:** Scan `.fpf/evidence/` for expired evidence. 4. **Count Decisions:** List files in `.fpf/decisions/`. 5. **Report to user.**
Status Report Format
## FPF Status
### Directory Structure
- [x] .fpf/ exists
- [x] knowledge/L0/ exists
- [x] knowledge/L1/ exists
- [x] knowledge/L2/ exists
- [x] evidence/ exists
- [x] decisions/ exists
### Current Phase
Based on hypothesis distribution: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE
### Hypothesis Counts
| Layer | Count | Status |
|-------|-------|--------|
| L0 (Proposed) | 3 | Awaiting verification |
| L1 (Verified) | 2 | Awaiting validation |
| L2 (Validated) | 1 | Ready for decision |
| Invalid | 1 | Rejected |
### Evidence Status
| Total | Fresh | Stale | Expired |
|-------|-------|-------|---------|
| 5 | 3 | 1 | 1 |
### Warnings
- 1 evidence file is EXPIRED: ev-benchmark-old-2024-06-15
- Consider running `/fpf:decay` to review stale evidence
### Recent Decisions
| DRR | Date | Winner |
|-----|------|--------|
| DRR-2025-01-15-use-redis | 2025-01-15 | redis-caching |
Phase Detection Logic
Determine current phase by examining the knowledge base state:
| Condition | Phase | Next Step | |-----------|-------|-----------| | No `.fpf/` directory | NOT INITIALIZED | Run `/fpf:propose-hypotheses` | | L0 > 0, L1 = 0, L2 = 0 | ABDUCTION | Continue with verification | | L1 > 0, L2 = 0 | DEDUCTION | Continue with validation | | L2 > 0, no recent DRR | INDUCTION | Continue with audit and decision | | Recent DRR exists | DECISION COMPLETE | Review decision | | All empty | IDLE | Run `/fpf:propose-hypotheses` |
Evidence Freshness Check
For each evidence file in `.fpf/evidence/`: 1. Read the `valid_until` field from frontmatter 2. Compare with current date 3. Classify:
- **Fresh**: `valid_until` > today + 30 days
- **Stale**: `valid_until` > today but < today + 30 days
- **Expired**: `valid_until` < today
If any evidence is stale or expired, warn the user and suggest `/fpf:decay`.
Example Output
## FPF Status
### Current Phase: DEDUCTION
You have 3 hypotheses in L0 awaiting verification.
Next step: Continue the FPF workflow to process L0 hypotheses.
### Hypothesis Counts
| Layer | Count |
|-------|-------|
| L0 | 3 |
| L1 | 0 |
| L2 | 0 |
| Invalid | 0 |
### Evidence Status
No evidence files yet (hypotheses not validated).
### No Warnings
All systems nominal.
Read more
name: status description: "Display the current state of the FPF knowledge base"
Status Check
Display the current state of the FPF knowledge base.
Action (Run-Time)
1. **Check Directory Structure:** Verify `.fpf/` exists and contains required subdirectories. 2. **Count Hypotheses:** List files in each knowledge layer:
- `.fpf/knowledge/L0/` (Proposed)
- `.fpf/knowledge/L1/` (Verified)
- `.fpf/knowledge/L2/` (Validated)
- `.fpf/knowledge/invalid/` (Rejected)
3. **Check Evidence Freshness:** Scan `.fpf/evidence/` for expired evidence. 4. **Count Decisions:** List files in `.fpf/decisions/`. 5. **Report to user.**
Status Report Format
## FPF Status ### Directory Structure - [x] .fpf/ exists - [x] knowledge/L0/ exists - [x] knowledge/L1/ exists - [x] knowledge/L2/ exists - [x] evidence/ exists - [x] decisions/ exists ### Current Phase Based on hypothesis distribution: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE ### Hypothesis Counts | Layer | Count | Status | |-------|-------|--------| | L0 (Proposed) | 3 | Awaiting verification | | L1 (Verified) | 2 | Awaiting validation | | L2 (Validated) | 1 | Ready for decision | | Invalid | 1 | Rejected | ### Evidence Status | Total | Fresh | Stale | Expired | |-------|-------|-------|---------| | 5 | 3 | 1 | 1 | ### Warnings - 1 evidence file is EXPIRED: ev-benchmark-old-2024-06-15 - Consider running `/fpf:decay` to review stale evidence ### Recent Decisions | DRR | Date | Winner | |-----|------|--------| | DRR-2025-01-15-use-redis | 2025-01-15 | redis-caching |
Phase Detection Logic
Determine current phase by examining the knowledge base state:
| Condition | Phase | Next Step | |-----------|-------|-----------| | No `.fpf/` directory | NOT INITIALIZED | Run `/fpf:propose-hypotheses` | | L0 > 0, L1 = 0, L2 = 0 | ABDUCTION | Continue with verification | | L1 > 0, L2 = 0 | DEDUCTION | Continue with validation | | L2 > 0, no recent DRR | INDUCTION | Continue with audit and decision | | Recent DRR exists | DECISION COMPLETE | Review decision | | All empty | IDLE | Run `/fpf:propose-hypotheses` |
Evidence Freshness Check
For each evidence file in `.fpf/evidence/`: 1. Read the `valid_until` field from frontmatter 2. Compare with current date 3. Classify:
- **Fresh**: `valid_until` > today + 30 days
- **Stale**: `valid_until` > today but < today + 30 days
- **Expired**: `valid_until` < today
If any evidence is stale or expired, warn the user and suggest `/fpf:decay`.
Example Output
## FPF Status ### Current Phase: DEDUCTION You have 3 hypotheses in L0 awaiting verification. Next step: Continue the FPF workflow to process L0 hypotheses. ### Hypothesis Counts | Layer | Count | |-------|-------| | L0 | 3 | | L1 | 0 | | L2 | 0 | | Invalid | 0 | ### Evidence Status No evidence files yet (hypotheses not validated). ### No Warnings All systems nominal.
A hand-crafted collection of advanced context engineering techniques and patterns with minimal token footprint, focused on improving agent result quality and predictability.
Repo: NeoLabHQ/context-engineering-kit
Other skills on context-engineering-kit.
- /agent-evaluation
Evaluate and improve Claude Code commands, skills, and agents. Use when testing prompt effectiveness, validating context engineering choices, or measuring improvement quality.
Open skill - /apply-anthropic-skill-best-practices
Comprehensive guide for skill development based on Anthropic's official best practices - use for complex skills requiring detailed structure
Open skill - /context-engineering
Understand the components, mechanics, and constraints of context in agent systems. Use when writing, editing, or optimizing commands, skills, or sub-agents prompts.
Open skill - /create-agent
Comprehensive guide for creating Claude Code agents with proper structure, triggering conditions, system prompts, and validation - combines official Anthropic best practices with proven patterns
Open skill - /create-command
Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration
Open skill - /create-hook
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
Open skill

