Skip to content
Back to skills

Ctx Status

ASecurity

Display the current state of the FPF knowledge base

  • 11 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
testing

Security analysis

A100/100

Scanned September 10, 2026

npx -y skills add luokai0/ai-agent-skills-by-luo-kai --skill ctx-status --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ctx Status?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ctx Status
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/luokai0-ctx-status/badge)](https://www.skillsdirectory.com/skills/luokai0-ctx-status)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
author: luo-kai
name: fpf: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

```markdown
## 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.
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.