traceary-session-history

Estrellas5

Forks0

Actualizado25 de abril de 2026 a las 06:24

Use when the user asks about prior Traceary sessions, event history, command audits, or what happened earlier in the workspace. Trigger on phrases like "Traceary", "session history", "audit trail", "recent events", or "what happened earlier".

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

duck8823

duck8823/traceary

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Empleados de archivosOficina y apoyo administrativo·SOC 43-4071

SKILL.md

readonly

name	traceary-session-history
description	Use when the user asks about prior Traceary sessions, event history, command audits, or what happened earlier in the workspace. Trigger on phrases like "Traceary", "session history", "audit trail", "recent events", or "what happened earlier".
version	1.0.0

Traceary session history

Use the packaged traceary MCP server as the default read path when the user asks about local agent history.

Preferred tools

session_status(action="latest"): most recent session metadata for the current workspace
session_status(action="active"): only when the user is asking about the still-open session
list_events: recent history without a keyword filter
search: keyword-driven lookups
get_context: summarize the lead-up around an event

Guardrails

Prefer the read tools above before suggesting direct SQLite inspection.
Do not call record_event(type="log") or record_event(type="audit") unless the user explicitly wants to record a new event.
Hooks already capture session boundaries and shell command audits, so avoid duplicating those writes manually.

Más de este repositorio

mismo repositorio

traceary-memory-remember

duck8823/traceary

Use ONLY when the user explicitly asks to remember a specific durable fact, decision, constraint, or preference. Trigger phrases — "覚えておいて", "remember that", "for the record", "save this as", "記憶しておいて", "メモして". Do NOT use for generic notes, status updates, or session summaries. The candidate lands in the review inbox; never auto-accepted.

2026-07-165

traceary-memory-review

duck8823/traceary

Use when the user asks to review Traceary memory candidates, pending memory inbox items, or to generate a session summary/handoff from current Traceary context. Trigger phrases — "Traceary inbox", "memory inbox", "pending memories", "review memory candidates", "記憶候補", "メモリ候補", "保留中の記憶", "session recap", "セッションまとめ", "summarize this session for next time". Do not trigger for generic status / cleanup / progress requests unless Traceary memory/session review is explicit.

2026-07-135

traceary-session-history

Explain the Traceary Claude plugin, its MCP tools, and the built-in hook workflow. Use when the user asks about Traceary in Claude Code or explicitly calls /traceary-help.

2026-04-095

name	traceary-session-history
description	Use when the user asks about prior Traceary sessions, event history, command audits, or what happened earlier in the workspace. Trigger on phrases like "Traceary", "session history", "audit trail", "recent events", or "what happened earlier".
version	1.0.0

Traceary session history

Use the packaged traceary MCP server as the default read path when the user asks about local agent history.

Preferred tools

session_status(action="latest"): most recent session metadata for the current workspace
session_status(action="active"): only when the user is asking about the still-open session
list_events: recent history without a keyword filter
search: keyword-driven lookups
get_context: summarize the lead-up around an event

Guardrails

Prefer the read tools above before suggesting direct SQLite inspection.
Do not call record_event(type="log") or record_event(type="audit") unless the user explicitly wants to record a new event.
Hooks already capture session boundaries and shell command audits, so avoid duplicating those writes manually.