aether-daily-recap
Use this skill when you need to write a grounded daily or period recap from reviewed structured activity: workstreams, highlights, a timeline, and open loops, with each material claim linked to a source identifier. It separates what the evidence shows from what it suggests and does not invent accomplishments. Trigger it when the user asks what they worked on, how a day or week went, or wants a summary they can share. For raw event normalization use aether-activity-structuring.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- aether-daily-recap
- license
- MIT
- metadata
- { "aether-kit-version": "0.2.0", "aether-skill-version": "1.0" }
- description
- Use this skill when you need to write a grounded daily or period recap from reviewed structured activity: workstreams, highlights, a timeline, and open loops, with each material claim linked to a source identifier. It separates what the evidence shows from what it suggests and does not invent accomplishments. Trigger it when the user asks what they worked on, how a day or week went, or wants a summary they can share. For raw event normalization use aether-activity-structuring.
02 资源文件 2
- 参考文档evals/evals.json1.7 KB
- 参考文档evals/trigger-queries.json1.0 KB
03 SKILL.md 正文
Daily recap
Explain what the approved evidence shows without inventing achievements.
Workflow
- Establish the date window and timezone, then read the reviewed structured records. Exclude pending and rejected material.
- Group related events into workstreams. Write a concise narrative, timeline, and open loops; include highlights only when sources support them.
- Link each material claim to source identifiers or paths. Mark uncertain context and distinguish a command run from a task completed.
- Return the recap in chat by default. Write a durable file only when requested, and route any later memory storage through
aether-privacy-reviewandaether-memory. - Check chronology, links, omissions, and a sample of claims against approved sources. Report scope and unresolved questions.
Gotchas
- Grouping into workstreams is an interpretation. Name the evidence that puts two events in the same stream, and keep singleton work as its own line.
- Highlights are a claim about value. If the sources only show activity, write activity.
- A recap in chat is transient by default. Only a requested file counts as a durable artifact, and even then it is not memory.
- Absence of an open loop is not a closed one. If no source shows a follow-up, report it as unobserved rather than finished.
Report
Return the date window, the workstreams, the source links behind each material claim, the open loops, the excluded material, and the checks run.
04 同仓库更多 Skills
aether-workflow
Use this skill when a request spans more than one stage of the Aether activity-to-memory flow: source intake, human privacy review, structuring, recaps, persistent memory, backup, or verification. It routes to the specialist skills, keeps approval separate from analysis, and fixes what counts as a claim. Trigger it when the user shares activity they want turned into a recap or saved memory, even if they never name Aether or the stages. For a repository 3D graph, use the repository inventory, relations, and graph skills instead.
aether-verification
Use this skill when you are about to claim that an Aether recap, memory file, backup, or repository graph is complete: check every requirement against current sources, prove rejected and redacted material is absent from durable artifacts, and reconcile graph nodes with the Git-visible inventory. It reports requirement-by-requirement results with the commands run and what stays unverified. Trigger it at the end of any Aether task that produces a deliverable. For the graph workflow use aether-repository-inventory first.
aether-source-intake
Use this skill when you need to gather only the local activity sources a user selected, such as shell history, notes, editor or browser exports, screenshots, or attached files, and to record timestamps and provenance for each record. It bounds the time range, deduplicates repeated records, and separates observed events from inferred context. Trigger it before any recap, memory, export, or backup work, and whenever the request is only a transient read of personal material. For approval and redaction use aether-privacy-review.
aether-repository-relations
Use this skill when you need to derive graph edges that can be defended: containment from real parent directories, and reference edges from paths or skill names that actually appear in a file, with the source file and matched target recorded. It keeps import, call, and runtime relations absent unless they are separately verified. Trigger it between aether-repository-inventory and aether-repository-graph-3d, and when someone asks how files in a repository relate to each other.
aether-repository-inventory
Use this skill when you need to establish exactly what a repository graph will contain before any layout is drawn: the checkout, revision, dirty worktree state, observation time, Git-visible files and directories, exclusions, and node IDs. It separates measured totals from display filters. Trigger it whenever a full-repository view is requested for the current working tree or a named revision, and before any claim about how complete a graph is. For edges use aether-repository-relations.
aether-repository-graph-3d
Use this skill when the user wants to generate and check an interactive, standalone 3D graph of a Git repository with a searchable text view, a keyboard-reachable file list, and separate legend entries for containment and reference edges. It runs the bundled renderer to write one local HTML file and makes no network request. Trigger it to explore a whole repository visually or to confirm the graph artifact's counts, exclusions, and accessibility behavior. Gather files and edges with the inventory and relations skills first.