How do I install the Titan Recall skill?

Run npx skillmds@latest add aibot88/titan-recall in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Titan Recall safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Titan Recall?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Titan Recall free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Titan Recall?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Titan Recall by aibot88 — Agent Skill

Name: Titan Recall
Rating: 4.2 (5 reviews)
Author: aibot88

Titan Recall

Retrieve Titan candidate memory records with source, record id, authority note, confidence, and verification path. Use when a Titan service-cohort route needs this explicit bounded step. Do not use for hidden background agents, silent mutation, unreviewed proof sovereignty, or memory canonization without owner confirmation.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

titan-recall

Intent

Use this skill to retrieve and present Titan remembrance records without treating recall as source truth.

Trigger boundary

Use this skill when:

a user asks what a Titan remembers
a session needs bearer memory candidates
Mneme needs recall with source refs and confidence

Do not use this skill when:

recall would replace owner-repo evidence
records lack source refs
confidence or authority notes cannot be shown

Inputs

query text
bearer id or Titan name
memory index path
time or session filter
verification target

Outputs

matching remembrance records
record ids and source refs
authority warning
confidence notes
verification path

Procedure

search the candidate memory index
filter by bearer or session when provided
return source-backed matches only
include confidence and authority limits
point to owner verification when needed

Contracts

The skill is explicit-only and must not be invoked as hidden background behavior.
Titan receipts, bridge ledgers, console state, and memory records are witnesses, not final owner truth.
Forge mutation and Delta judgment gates must remain distinct and visible.
Owner-repo validation and human judgment remain stronger than the local skill output.

Risks and anti-patterns

treating Titan vocabulary as permission to widen authority
letting receipt or replay state replace owner-repo evidence
auto-approving Forge or Delta because a plan looks plausible
canonizing candidate memory without source-owned confirmation

Verification

confirm the request and outputs stayed inside the declared Titan lane
confirm any mutation or judgment gate was explicit and recorded
confirm source refs, receipt refs, or ledger refs are preserved when available
confirm the result names stop lines and remaining owner validation needs

Technique traceability

Pending Titan workflow techniques:

AOA-T-PENDING-TITAN-GATE-DISCIPLINE
AOA-T-PENDING-TITAN-RECEIPT-LINEAGE

Adaptation points

Replace pending technique refs with published aoa-techniques refs after the Titan workflow techniques are promoted.
Keep repo-local command examples in owner docs or examples rather than hard-coding them into the skill law.
If a Titan surface graduates from scaffold to reviewed, add review evidence before changing status.

---name: titan-recalldescription: Retrieve Titan candidate memory records with source, record id, authority note, confidence, and verification path. Use when a Titan service-cohort route needs this explicit bounded step. Do not use for hidden background agents, silent mutation, unreviewed proof sovereignty, or memory canonization without owner confirmation.license: Apache-2.0---# titan-recall## IntentUse this skill to retrieve and present Titan remembrance records without treating recall as source truth.## Trigger boundaryUse this skill when:- a user asks what a Titan remembers- a session needs bearer memory candidates- Mneme needs recall with source refs and confidenceDo not use this skill when:- recall would replace owner-repo evidence- records lack source refs- confidence or authority notes cannot be shown## Inputs- query text- bearer id or Titan name- memory index path- time or session filter- verification target## Outputs- matching remembrance records- record ids and source refs- authority warning- confidence notes- verification path## Procedure1. search the candidate memory index2. filter by bearer or session when provided3. return source-backed matches only4. include confidence and authority limits5. point to owner verification when needed## Contracts- The skill is explicit-only and must not be invoked as hidden background behavior.- Titan receipts, bridge ledgers, console state, and memory records are witnesses, not final owner truth.- Forge mutation and Delta judgment gates must remain distinct and visible.- Owner-repo validation and human judgment remain stronger than the local skill output.## Risks and anti-patterns- treating Titan vocabulary as permission to widen authority- letting receipt or replay state replace owner-repo evidence- auto-approving Forge or Delta because a plan looks plausible- canonizing candidate memory without source-owned confirmation## Verification- confirm the request and outputs stayed inside the declared Titan lane- confirm any mutation or judgment gate was explicit and recorded- confirm source refs, receipt refs, or ledger refs are preserved when available- confirm the result names stop lines and remaining owner validation needs## Technique traceabilityPending Titan workflow techniques:- AOA-T-PENDING-TITAN-GATE-DISCIPLINE- AOA-T-PENDING-TITAN-RECEIPT-LINEAGE## Adaptation points- Replace pending technique refs with published aoa-techniques refs after the Titan workflow techniques are promoted.- Keep repo-local command examples in owner docs or examples rather than hard-coding them into the skill law.- If a Titan surface graduates from scaffold to reviewed, add review evidence before changing status.

Frequently asked questions