Skip to content
Back to skills

Lifecycle Report

ASecurity

Scan project memory for v1.7.1 lifecycle frontmatter · report tier distribution + promotion candidates (reinforce_count >= promote_after) · NO LLM.

  • 1,253 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
ai-agents

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add chunxiaoxx/nautilus-compass --skill lifecycle_report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lifecycle Report?

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

Security grade badge for Lifecycle Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/chunxiaoxx-lifecycle-report/badge)](https://www.skillsdirectory.com/skills/chunxiaoxx-lifecycle-report)

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
---
name: lifecycle_report
status: codified
version: 1.0.0
tier: episodic
description: Scan project memory for v1.7.1 lifecycle frontmatter · report tier distribution + promotion candidates (reinforce_count >= promote_after) · NO LLM.
inputs:
  - project (str, optional): project slug · defaults to active project
  - mem_dir (path, optional): override · skip project resolution
outputs:
  - tier_distribution (counts by working/episodic/semantic/procedural/unset)
  - decay_status (now_active/expired/never)
  - promotion_candidates (list of {path, current_tier, next_tier, reinforce_count, promote_after})
  - total_memories
---

# lifecycle_report

Aggregate the 4-tier lifecycle schema landed in v1.7.1 across a project's
memory directory. Identifies memories ripe for tier promotion using the
LLM-free deterministic rule: `reinforce_count >= promote_after`.

## When to use

- Pre-promotion audit: which working-tier memories should be promoted to
  episodic? Which episodic to semantic?
- Decay sweep: which memories have hit their `forget_at` ISO8601 timestamp?
- Tier health check: ratio of working/episodic/semantic/procedural memories.

## Why codified

- Frontmatter parsing is stable (won't change · v1.7.1 fixed schema)
- Deterministic output · no LLM
- Used by the 4-tier paradigm validation per paper3 cite (llm-wiki2 fuse)

Files in this skill

  • SKILL.md1.3 KB
  • handler.py4.8 KB

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.