CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-history-ingest

Unified wiki-history-ingest entrypoint for conversation/session sources. Use this when the user says "/wiki-history-ingest claude" or "/wiki-history-ingest codex", or asks to ingest agent history without naming the underlying skill. This router dispatches to the specialized history skill.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Unified History Ingest Router

This is a thin router for history sources only. It does not replace wiki-ingest for documents.

Subcommands

If the user invokes /wiki-history-ingest <target> (or equivalent text command), dispatch directly:

SubcommandRoute To
claudeclaude-history-ingest
codexcodex-history-ingest
autoinfer from context using rules below

Routing Rules

  1. If the user explicitly says claude or codex, route directly.
  2. If the user provides a path/source:
    • ~/.claude or Claude memory/session JSONL artifacts -> claude-history-ingest
    • ~/.codex or rollout/session index artifacts -> codex-history-ingest
  3. If ambiguous, ask one short clarification:
    • "Should I ingest claude or codex history?"
  4. If the user asks for another history source, say that only claude and codex history ingesters are installed in this repository.

Execution Contract

  • After routing, execute the destination skill's workflow exactly.
  • Do not duplicate destination logic in this file.
  • Leave manifest/index/log update semantics to the destination skill.

UX Convention

  • Use wiki-ingest for documents/content sources
  • Use wiki-history-ingest for agent history sources

Examples:

  • /wiki-history-ingest claude
  • /wiki-history-ingest codex
  • $wiki-history-ingest claude (agents that use $skill invocation)
Repository

saski/arnesto

Path

.agents/skills/wiki-history-ingest/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.