aether-privacy-review
Use this skill when you need to decide what may become persistent. It shows the user the candidate material with source, time, and PII or secret hints, records approve, redact, exclude, or purge decisions, and applies redaction to the content that flows downstream. Trigger it before writing any memory file, export, or backup, and whenever the user asks to remove something that was already stored. It never approves material on the user's behalf. For gathering sources use aether-source-intake.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- aether-privacy-review
- license
- MIT
- metadata
- { "aether-kit-version": "0.2.0", "aether-skill-version": "1.0" }
- description
- Use this skill when you need to decide what may become persistent. It shows the user the candidate material with source, time, and PII or secret hints, records approve, redact, exclude, or purge decisions, and applies redaction to the content that flows downstream. Trigger it before writing any memory file, export, or backup, and whenever the user asks to remove something that was already stored. It never approves material on the user's behalf. For gathering sources use aether-source-intake.
02 资源文件 2
- 参考文档evals/evals.json1.9 KB
- 参考文档evals/trigger-queries.json1.1 KB
03 SKILL.md 正文
Privacy review
Make the candidate material understandable so the user can choose what may persist.
Workflow
- Present source, time, a minimal preview or safe summary, and any likely secret or PII hint. Detection is advisory; avoid printing the full sensitive value.
- Record explicit user choices for approve, redact, exclude, or purge. A prior request for a recap does not automatically approve a permanent memory file.
- Apply redaction to the content handed downstream, not only to the display. Keep rejected material out of recaps when the user excluded it and out of all durable memory, exports, and backup.
- Recheck eligibility immediately before any file write or external transmission. On a correction or deletion, locate related derived claims and artifacts for removal or rebuild.
- Verify with distinct synthetic approved and rejected sentinels. Report what was approved, what remains pending, and which downstream artifacts were checked.
Gotchas
- Redacting only the preview is the most common failure. The downstream record, the memory file, and the export all need the redacted text.
- A deletion in one place leaves derived copies behind: recaps, indexes, summaries, and old archives that quote the removed material.
- Sentinel checks need synthetic material that cannot be confused with real content. Use an unmistakable marker, and confirm it is absent rather than merely unreported.
- A pending item is not a rejected item, but neither is it approved. Both stay out of durable storage until the user answers.
Guardrails
Never approve private material on the user's behalf. Do not retain deleted payloads in an audit note. The aether-verification skill covers a cross-stage exclusion check.
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.