— No reviews yet
0 installs
7 views
0.0% view→install
Install
$ agentstack add skill-8dionysus-aoa-skills-titan-event-replay ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Titan Event Replay? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
titan-event-replay
Intent
Use this skill to replay Titan event logs and compare the resulting state to current bridge or console state.
Trigger boundary
Use this skill when:
- bridge state must be reconstructed from events
- a digest or approval queue needs replay evidence
- metrics or closeout need traceable event order
Do not use this skill when:
- events are missing source refs
- replay output would be treated as proof or memory canon
- replay would mutate state without an explicit write target
Inputs
- event log path
- optional current state path
- thread or turn filter
- receipt ref
- expected replay target
Outputs
- replayed state summary
- event order report
- differences from current state
- authority warning
- next verification step
Procedure
- select the bridge or console event stream and its source refs
- replay events into inspectable derived state without granting authority
- preserve gaps, ordering uncertainty, and replay limits in the output
- compare replayed gate state against receipts or ledger refs when available
- name whether the replay supports review, repair, or only further inspection
Contracts
- The skill is explicit-only and must not be invoked as hidden background behavior.
- Titan role, helper/control-plane, runtime implementation, memory, proof, and public-runbook authority stays in owner repositories: aoa-agents, aoa-sdk, abyss-stack, aoa-memo, aoa-evals, and 8Dionysus.
- Receipts, bridge ledgers, console state, replay artifacts, approval records, and memory records are witnesses or candidates, not final owner truth.
- Forge mutation and Delta judgment gates must remain distinct, operator-visible, and receipt-linked.
- Missing source refs, missing approval, missing validation, or unclear owner route must be named as stop conditions.
Risks and anti-patterns
- treating Titan vocabulary as permission to widen authority
- letting receipt, replay, console, or bridge state replace owner-repo evidence
- auto-approving Forge or Delta because a plan looks plausible
- promoting candidate memory, approvals, replay, or receipts into canon without owner review
- using the skill for an ordinary repo task that has no explicit Titan route
Verification
- confirm direct skill invocation or explicit Titan service-cohort request is present
- confirm lane, gate, source refs, and owner surface are named when relevant
- confirm Forge or Delta locked or allowed state matches recorded approval evidence
- confirm generated artifacts are marked witness, candidate, derived, or advisory rather than final truth
- confirm next validation, replay, repair, or owner-route follow-up is named before continuation
Technique traceability
Manifest-backed techniques:
- AOA-T-0066 from
8Dionysus/aoa-techniquesat3b1d5d623569aa4920b87280d0db0e911d2e29d5using pathtechniques/history/history-artifacts/transcript-replay-artifact/TECHNIQUE.mdand sections: Intent, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0045 from
8Dionysus/aoa-techniquesat3b1d5d623569aa4920b87280d0db0e911d2e29d5using pathtechniques/history/history-artifacts/witness-trace-as-reviewable-artifact/TECHNIQUE.mdand sections: Intent, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0043 from
8Dionysus/aoa-techniquesat3b1d5d623569aa4920b87280d0db0e911d2e29d5using pathtechniques/instruction/capability-boundary/multi-source-primary-input-provenance/TECHNIQUE.mdand sections: Intent, Inputs, Outputs, Core procedure, Contracts, Risks, Validation
Adaptation points
- Extract a Titan-specific reusable technique into aoa-techniques only after repeated reviewed evidence exists; do not add pending IDs as placeholders.
- Keep repo-local command examples in owner docs or examples rather than hard-coding them into skill law.
- If a Titan surface graduates from scaffold to reviewed or evaluated, add review evidence before changing status.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: 8Dionysus
- Source: 8Dionysus/aoa-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.