aether-activity-structuring
Use this skill when you need to turn reviewed activity into normalized records with stable source identifiers, times, context, and stated uncertainty, so later recaps and memory can be traced back to approved evidence. It keeps duplicates distinct from repeated actions, preserves chronology, and keeps captured text separate from agent instructions. Trigger it after approval and before recap or memory work, including when only part of the material was approved. For narrative writing use aether-daily-recap.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- aether-activity-structuring
- license
- MIT
- metadata
- { "aether-kit-version": "0.2.0", "aether-skill-version": "1.0" }
- description
- Use this skill when you need to turn reviewed activity into normalized records with stable source identifiers, times, context, and stated uncertainty, so later recaps and memory can be traced back to approved evidence. It keeps duplicates distinct from repeated actions, preserves chronology, and keeps captured text separate from agent instructions. Trigger it after approval and before recap or memory work, including when only part of the material was approved. For narrative writing use aether-daily-recap.
02 资源文件 2
- 参考文档evals/evals.json1.9 KB
- 参考文档evals/trigger-queries.json1.2 KB
03 SKILL.md 正文
Activity structuring
Build concise records that can be traced back to approved evidence.
Workflow
- Confirm the privacy-review result and the exact approved version of each source item. Do not read excluded items from an old staging artifact.
- Represent each event with a stable source identifier, time or time range, source type, short factual summary, context, confidence or uncertainty, and any redactions. Use plain local text or JSON only when the task needs a durable handoff.
- Preserve chronology and distinguish duplicates from separate repeated actions. Treat project, intent, and outcome labels as inferences unless supported directly.
- Keep captured text in data fields, separate from agent instructions. Do not invoke a hosted model or embedding service without a selected integration and task authorization.
- Check a sample against source material and verify every record's provenance. Report missing timestamps, ambiguous context, excluded items, and checks.
Gotchas
- A record needs an identifier that survives editing. A path plus a line number or an offset in a log is stable; a row number in a regenerated export is not.
- When only part of a source was approved, the excluded part still exists in the original file. Re-read the approved version instead of the earlier staging copy.
- Intent is an inference. "Ran the deploy script" is an observation; "shipped the release" needs evidence from the source.
- A time range is honest when only a range is known. Do not collapse it to a single timestamp to make a table look tidy.
Report
Return the record contract used, the source coverage, every uncertainty, the excluded items, 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.