status
installsforks
How to install status?
neolabhq/context-engineering-kit/status
$npx -y skills add NeoLabHQ/context-engineering-kit --skill statusDisplay the current state of the FPF knowledge base
SKILL.md
| 1 | # Status Check |
| 2 | |
| 3 | Display the current state of the FPF knowledge base. |
| 4 | |
| 5 | ## Action (Run-Time) |
| 6 | |
| 7 | 1. **Check Directory Structure:** Verify `.fpf/` exists and contains required subdirectories. |
| 8 | 2. **Count Hypotheses:** List files in each knowledge layer: |
| 9 | - `.fpf/knowledge/L0/` (Proposed) |
| 10 | - `.fpf/knowledge/L1/` (Verified) |
| 11 | - `.fpf/knowledge/L2/` (Validated) |
| 12 | - `.fpf/knowledge/invalid/` (Rejected) |
| 13 | 3. **Check Evidence Freshness:** Scan `.fpf/evidence/` for expired evidence. |
| 14 | 4. **Count Decisions:** List files in `.fpf/decisions/`. |
| 15 | 5. **Report to user.** |
| 16 | |
| 17 | ## Status Report Format |
| 18 | |
| 19 | ```markdown |
| 20 | ## FPF Status |
| 21 | |
| 22 | ### Directory Structure |
| 23 | - [x] .fpf/ exists |
| 24 | - [x] knowledge/L0/ exists |
| 25 | - [x] knowledge/L1/ exists |
| 26 | - [x] knowledge/L2/ exists |
| 27 | - [x] evidence/ exists |
| 28 | - [x] decisions/ exists |
| 29 | |
| 30 | ### Current Phase |
| 31 | Based on hypothesis distribution: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE |
| 32 | |
| 33 | ### Hypothesis Counts |
| 34 | |
| 35 | | Layer | Count | Status | |
| 36 | |-------|-------|--------| |
| 37 | | L0 (Proposed) | 3 | Awaiting verification | |
| 38 | | L1 (Verified) | 2 | Awaiting validation | |
| 39 | | L2 (Validated) | 1 | Ready for decision | |
| 40 | | Invalid | 1 | Rejected | |
| 41 | |
| 42 | ### Evidence Status |
| 43 | |
| 44 | | Total | Fresh | Stale | Expired | |
| 45 | |-------|-------|-------|---------| |
| 46 | | 5 | 3 | 1 | 1 | |
| 47 | |
| 48 | ### Warnings |
| 49 | |
| 50 | - 1 evidence file is EXPIRED: ev-benchmark-old-2024-06-15 |
| 51 | - Consider running `/fpf:decay` to review stale evidence |
| 52 | |
| 53 | ### Recent Decisions |
| 54 | |
| 55 | | DRR | Date | Winner | |
| 56 | |-----|------|--------| |
| 57 | | DRR-2025-01-15-use-redis | 2025-01-15 | redis-caching | |
| 58 | ``` |
| 59 | |
| 60 | ## Phase Detection Logic |
| 61 | |
| 62 | Determine current phase by examining the knowledge base state: |
| 63 | |
| 64 | | Condition | Phase | Next Step | |
| 65 | |-----------|-------|-----------| |
| 66 | | No `.fpf/` directory | NOT INITIALIZED | Run `/fpf:propose-hypotheses` | |
| 67 | | L0 > 0, L1 = 0, L2 = 0 | ABDUCTION | Continue with verification | |
| 68 | | L1 > 0, L2 = 0 | DEDUCTION | Continue with validation | |
| 69 | | L2 > 0, no recent DRR | INDUCTION | Continue with audit and decision | |
| 70 | | Recent DRR exists | DECISION COMPLETE | Review decision | |
| 71 | | All empty | IDLE | Run `/fpf:propose-hypotheses` | |
| 72 | |
| 73 | ## Evidence Freshness Check |
| 74 | |
| 75 | For each evidence file in `.fpf/evidence/`: |
| 76 | 1. Read the `valid_until` field from frontmatter |
| 77 | 2. Compare with current date |
| 78 | 3. Classify: |
| 79 | - **Fresh**: `valid_until` > today + 30 days |
| 80 | - **Stale**: `valid_until` > today but < today + 30 days |
| 81 | - **Expired**: `valid_until` < today |
| 82 | |
| 83 | If any evidence is stale or expired, warn the user and suggest `/fpf:decay`. |
| 84 | |
| 85 | ## Example Output |
| 86 | |
| 87 | ``` |
| 88 | ## FPF Status |
| 89 | |
| 90 | ### Current Phase: DEDUCTION |
| 91 | |
| 92 | You have 3 hypotheses in L0 awaiting verification. |
| 93 | Next step: Continue the FPF workflow to process L0 hypotheses. |
| 94 | |
| 95 | ### Hypothesis Counts |
| 96 | |
| 97 | | Layer | Count | |
| 98 | |-------|-------| |
| 99 | | L0 | 3 | |
| 100 | | L1 | 0 | |
| 101 | | L2 | 0 | |
| 102 | | Invalid | 0 | |
| 103 | |
| 104 | ### Evidence Status |
| 105 | |
| 106 | No evidence files yet (hypotheses not validated). |
| 107 | |
| 108 | ### No Warnings |
| 109 | |
| 110 | All systems nominal. |
| 111 | ``` |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
