菜单
This skill should be used when the user asks for "freshness check", "freshness report", "what needs attention", "stale items", "review backlog", or mentions wanting to see what secondbrain content needs review or updating.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks to "create a tortoise model", "new tortoise project", "tortoise orm", "async orm", "aerich migration", "fastapi tortoise", "tortoise model abstract", "tortoise base class", or mentions Tortoise ORM project structure, model organization, querysets, signals, transactions, or testing. Provides opinionated enterprise patterns: model-per-file, abstract Base interfaces for mocks/transitions, strict class member ordering, FastAPI lifespan, built-in Tortoise migrations (never Aerich), Pydantic v2, pytest.
Use when the user wants to embed an architecture diagram directly inside a React/Vite site as inline SVG (no html2canvas, no external scripts, no separate HTML file). Produces an `arch-diagram` fenced markdown block that the site's React renderer expands — including `<lucide-icon>` placeholders for semantic icons. Companion to the `architecture-diagram` skill, which produces standalone HTML.
Use when the user asks for a system, infrastructure, cloud, security, network topology, or architecture diagram. Produces polished dark-themed self-contained HTML+SVG files with mathematically-correct label placement, clean-background priority, text halos, and leader lines.
Use when the user asks for a mindmap, mind-map, concept map, idea tree, brainstorm diagram, or any radial topic explosion ("draw a mindmap of X", "map out the themes around Y", "mindmap the differentiators of Z"). Produces dark-themed self-contained HTML+SVG with a central root, branches radiating in all directions, halo text, Q-curved Bezier connectors, and geometry-audit gating.
Use when the user asks for a sequence diagram, ladder diagram, message-exchange diagram, or any temporal flow showing who talks to whom in order ("draw the OAuth flow", "show the request lifecycle", "diagram the protocol over time", "sequence diagram for X"). Produces dark-themed self-contained SVG with actor lifelines, sync/async/return messages, self-loops, halo text, and a geometry-audit gate that knows about lifelines.
This skill should be used when the user asks to "create ADR", "document decision", "architecture decision", "add decision record", or mentions needing to record a technical decision with status tracking and category organization.
| name | secondbrain-freshness |
| description | This skill should be used when the user asks for "freshness check", "freshness report", "what needs attention", "stale items", "review backlog", or mentions wanting to see what secondbrain content needs review or updating. |
Generate a comprehensive freshness report for all secondbrain entities.
Verify secondbrain is initialized:
.claude/data/config.yamlRead .claude/data/config.yaml to get:
For each enabled entity:
Format by entity and urgency:
## Freshness Report
Generated: 2026-01-15 10:30
### Summary
| Entity | Critical | Stale | Warning | OK |
|--------|----------|-------|---------|-----|
| ADRs | 2 | 5 | 3 | 12 |
| Tasks | 0 | 8 | 4 | 15 |
| Notes | 1 | 3 | 6 | 25 |
| Discussions | 0 | 2 | 1 | 10 |
**Total needing attention:** 30 items
---
### Critical (Needs Immediate Attention)
#### ADRs (2 items)
| ID | Title | Status | Age |
|----|-------|--------|-----|
| ADR-0003 | API Gateway Selection | proposed | 95 days |
| ADR-0007 | Database Migration | draft | 78 days |
#### Notes (1 item)
| ID | Title | Age |
|----|-------|-----|
| 2025-10-01-legacy-system | Legacy System Overview | 106 days |
---
### Stale (Should Review)
#### Tasks (8 items)
| ID | Title | Status | Priority | Age |
|----|-------|--------|----------|-----|
| TASK-0012 | Update documentation | in_progress | medium | 45 days |
| TASK-0015 | Fix login bug | todo | high | 42 days |
...
---
### Recommended Actions
1. **ADR-0003:** 95 days in "proposed" status
- Action: Review and move to admitted/rejected
2. **ADR-0007:** 78 days in "draft" status
- Action: Complete draft or cancel
3. **TASK-0012:** 45 days in progress
- Action: Check if blocked, update status
4. **2025-10-01-legacy-system:** 106 days old note
- Action: Archive or update content
For each critical/stale item, offer specific actions:
Update .claude/data/config.yaml:
meta:
last_freshness_check: 2026-01-15T10:30:00
Default thresholds (configurable per entity):
| Entity | Default | Critical |
|---|---|---|
| ADRs | 30 days | 60 days |
| Tasks | 14 days | 28 days |
| Notes | 30 days | 60 days |
| Discussions | 7 days | 14 days |
Skip items with terminal statuses:
## Freshness Summary
- **Critical:** 3 items need immediate attention
- **Stale:** 18 items should be reviewed
- **Warning:** 13 items approaching staleness
Run with `--detailed` for full breakdown.
Complete breakdown with tables and recommendations (default).
{
"generated": "2026-01-15T10:30:00",
"summary": {
"critical": 3,
"stale": 18,
"warning": 13,
"ok": 62
},
"by_entity": {
"adrs": { "critical": 2, "stale": 5, ... },
...
},
"items": [...]
}