Status
- 846 installs
- 1.3k repo stars
- Updated July 26, 2026
- neolabhq/context-engineering-kit
status is a Claude Code skill that snapshots the FPF `.fpf/` knowledge base by reporting hypothesis layer counts, evidence freshness, and decision files before the next context-engineering step.
About
status is a Claude Code skill from neolabhq/context-engineering-kit that displays the current state of the FPF (`.fpf/`) knowledge base at runtime. The skill verifies `.fpf/` directory structure, counts hypothesis files across four knowledge layers—L0 Proposed, L1 Verified, L2 Validated, and invalid Rejected—scans `.fpf/evidence/` for expired evidence, and lists decision files under `.fpf/decisions/`. Developers reach for status before continuing context-engineering work when they need a ground-truth snapshot of what is proposed, verified, validated, or rejected. Output follows a structured markdown status report format defined in the skill. status is a read-only health check, not a hypothesis authoring or evidence ingestion tool.
- Verifies `.fpf/` directory tree and required knowledge/evidence/decision folders
- Counts hypotheses per layer: L0 Proposed, L1 Verified, L2 Validated, plus invalid/rejected
- Evidence freshness scan with fresh/stale/expired totals and named stale warnings
- Infers current FPF phase: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE
- Structured markdown status report for the user including recent decisions table
Status by the numbers
- 846 all-time installs (skills.sh)
- +46 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #555 of 3,301 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/neolabhq/context-engineering-kit --skill statusAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 846 |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 26, 2026 |
| Repository | neolabhq/context-engineering-kit ↗ |
What is the current state of FPF knowledge?
Snapshot the FPF (`.fpf/`) knowledge base—hypothesis layers, evidence freshness, and decisions—before the next context-engineering step.
Who is it for?
Developers using the FPF `.fpf/` knowledge base who need a quick structural snapshot before the next context-engineering session.
Skip if: Projects without an `.fpf/` directory or teams that do not use the FPF hypothesis-evidence-decision workflow.
When should I use this skill?
A user asks for FPF status, knowledge base health, hypothesis counts, or evidence freshness before continuing work.
What you get
Markdown status report with hypothesis layer counts, evidence freshness flags, and decision inventory.
- FPF markdown status report
By the numbers
- Reports hypothesis counts across 4 FPF knowledge layers: L0, L1, L2, and invalid
Files
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.Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.645k185kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.547k185k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.466kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).466kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.466kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.465kFAQ
What directories does status inspect in FPF?
status checks `.fpf/` structure, counts files in `.fpf/knowledge/L0/`, `L1/`, `L2/`, and `invalid/`, scans `.fpf/evidence/` for expiry, and lists `.fpf/decisions/`.
When should developers run the status skill?
status should run before the next context-engineering step when teams need current hypothesis layer counts, stale evidence alerts, and a decision inventory from the FPF knowledge base.
Is Status safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.