- Home
- Skills
- Research & Analysis
- 04 — Chronicle Necromancer · Complete Edition
Works with the AI Agents you already use
04 — Chronicle Necromancer · Complete Edition
Retains causal reconstruction and authority timelines, then makes those methods useful for message threads, decision histories, disputes and lost handoffs.
$25
04 — Chronicle Necromancer · Complete Edition
Example session with this skill installed
Everyday request
Here are the messages and receipts. Build the timeline, show where the accounts disagree, and tell me which missing detail would settle it.
For a reproducible local example, use the included synthetic structured fixture:
{
"events": [
{
"id": "request",
"time": "2026-11-10T10:00:00+00:00",
"text": "Request recorded"
},
{
"id": "effect",
"time": "2026-11-10T09:00:00+00:00",
"text": "Effect recorded",
"after": [
"request"
]
},
{
"id": "note",
"text": "Undated follow-up"
}
]
}
Run the class's packaged helper on that fixture. Show the readable result, full structured output, executed Thirsty calculation and the limits of what was demonstrated.
- Read your context and instructions
- Compiled the output
Chronicle Necromancer — real local worked example
Example type: Actual execution of the packaged structured helper on synthetic input. This is not a claimed live customer session or a full specialist-model benchmark.
Readable work product
Recorded timeline:
- 2026-11-10T09:00:00+00:00: Effect recorded
- 2026-11-10T10:00:00+00:00: Request recorded
Undated records: 1
Causal/time conflicts requiring follow-up: 1
Recorded time order; clock accuracy and completeness not established
Complete structured result
{
"contradictions": [
{
"event": "effect",
"must_follow": "request",
"problem": "Recorded clock order conflicts with supplied causal order"
}
],
"interpretation": "Recorded time order; clock accuracy and completeness not established",
"ordered_records": [
{
"after": [
"request"
],
"id": "effect",
"text": "Effect recorded",
"time": "2026-11-10T09:00:00+00:00"
},
{
"id": "request",
"text": "Request recorded",
"time": "2026-11-10T10:00:00+00:00"
}
],
"undated": [
{
"id": "note",
"text": "Undated follow-up"
}
]
}
Executed Thirsty-lang calculation
module conclave: core
drink result = 3 - 1
pour result
The helper checked the language result independently, encoded the complete structured result using the published TSCG-B codec, decoded it and compared the text. Running the standalone helper generates the result files and execution receipt. The example shown here was produced on the supplied synthetic input.
The deeper specialist use
Request: A request was recorded at 10:00, revocation at 10:01, effect at 10:02 and worker observation at 10:03. Reconstruct the possibilities without assuming synchronized clocks.
Illustrative specialist response: Keep four questions separate: when the event occurred, when it was recorded, when authority changed and when the worker learned about it. If revocation was immediately effective and clocks align, the recorded effect follows revocation. If the rule makes receipt decisive, the interpretation may differ. Clock uncertainty can also change the ordering. The deliverable retains supported histories and asks for the effective-time rule, clock provenance and delivery records before declaring one history established.
The preceding specialist response is an authored illustration, not an executed external action. The original class procedures and supporting skills remain included for an actual authorized assignment.
Next step
Replace the fixture with your own task data after checking that it fits the helper's input model, or use the conversational workflow directly with your AI host. Use a fresh output directory; the helper refuses to overwrite an existing result. Review factual classifications and missing inputs before relying on the result.
Connects securely to your tools. The creator never sees your data.
About this skill
Chronicle Necromancer — Complete Edition
Recover the history hiding inside the fragments.
Retains causal reconstruction and authority timelines, then makes those methods useful for message threads, decision histories, disputes and lost handoffs.
One class. 47 equipped skills. The original specialist method plus six practical everyday workflows. $25 as a one-time purchase.
For reconstructing decisions, project changes, customer-service problems, and confusing handoffs. For deeper work, the class retains its original specialist equipment and source-defined method: Which histories fit the evidence, and what observation distinguishes them?
What you actually receive
- All 40 original skills, including the specialist entrypoint, original supporting procedures, language workbench and evaluation lab.
- Six added everyday skills, listed in full below, and the new structured helper and worked example.
- 1 restored named dependency/dependencies: epistemic-status-enforcer.
- Class methods, contracts, source references, standalone task-packet tooling, executable helpers and worked examples, delivered through your connected AI.
- Standalone Thirsty-lang and TSCG-B tooling that uses the real
thirsty-lang==0.9.0runtime. Code execution requires Python 3.10+, a host execution tool and that separately installed package in the same environment. No runtime wheel is delivered through Agensi.
The specialist class: the original depth stays equipped
- Preserve source records and separate each time dimension.
- Construct a partial causal order from witnessed dependencies rather than file order alone.
- Apply clock bounds without inventing absent timestamps.
- Enumerate bounded evidence-consistent histories or a compact constraint representation.
- Evaluate authority at possible action times for each supported history.
- Identify contradictions and the observation that would eliminate each ambiguity.
- Return supported histories with explicit uncertainty and reproducible ordering constraints.
Specialist deliverable: history_reconstruction. Its source-defined result fields are event_bindings, time_provenance, causal_constraints, possible_histories, authority_windows, distinguishing_observations. These guide the work product; an actual outcome requires the task inputs, authorized tools and evidence.
Six everyday workflows — the documented practical use cases
1. Reconstruct events across a message thread
Preserve quotations and message times, distinguish what a message claims from what it proves, and keep undated events outside the strict ordering.
2. Recover why a decision changed
Separate proposals, approvals and executed changes. Identify the last supported decision and preserve unresolved dissent instead of rewriting history.
3. Organize a customer-service record
Arrange supplied receipts, promises and contacts, identify mismatched references and draft a factual summary. Do not assert legal entitlement or invent missing correspondence.
4. Find what was lost between people or sessions
Compare what was sent, acknowledged and later observed. Produce an evidence-backed handoff record and the smallest questions needed to close gaps.
5. Explain how a document or plan evolved
Compare supplied versions and timestamps, attribute actual text changes, and distinguish author identity from file metadata.
6. Reconstruct a technical incident with uncertain clocks
Separate occurrence, recording, observation and authority times. Use causal constraints and clock bounds; retain multiple histories when the evidence cannot distinguish them.
Example 1 — what a specialist assignment can look like
You ask: A request was recorded at 10:00, revocation at 10:01, effect at 10:02 and worker observation at 10:03. Reconstruct the possibilities without assuming synchronized clocks.
Illustrative response: Keep four questions separate: when the event occurred, when it was recorded, when authority changed and when the worker learned about it. If revocation was immediately effective and clocks align, the recorded effect follows revocation. If the rule makes receipt decisive, the interpretation may differ. Clock uncertainty can also change the ordering. The deliverable retains supported histories and asks for the effective-time rule, clock provenance and delivery records before declaring one history established.
This example illustrates the class method. It is not an assertion that the proposed external investigation, model trial or system change has been executed.
Example 2 — an everyday request
Here are the messages and receipts. Build the timeline, show where the accounts disagree, and tell me which missing detail would settle it.
The work product: A source-linked timeline, competing explanations, contradictions, and a short list of decisive follow-up questions.
The included local helper demonstrates a bounded part of this workflow. Its actual run on synthetic structured input produced:
Recorded timeline:
- 2026-11-10T09:00:00+00:00: Effect recorded
- 2026-11-10T10:00:00+00:00: Request recorded
Undated records: 1
Causal/time conflicts requiring follow-up: 1
Recorded time order; clock accuracy and completeness not established
See the demo section below for its complete input, structured result and executed Thirsty calculation.
Example 3 — using the class template on your own material
Use Chronicle Necromancer — Complete Edition.
Goal: [the concrete result I need]
Material: [paste or attach the actual records, notes, code or facts]
Scope: [what may be inspected or changed]
Constraints: [time window, dependencies, formats and important conditions]
Deliver: A source-linked timeline, competing explanations, contradictions, and a short list of decisive follow-up questions.
Use the original specialist method when the problem requires it.
Ask only for missing facts that materially change the result.
Show what you actually did and what still needs a decision.
For a simple request, use only the relevant everyday mode. For advanced work, select the original specialist procedures. Keeping the equipment available does not require loading every skill into every interaction.
Every skill available in this pack (47 total)
-
algorithm-design-forge — Invent and implement problem-specific algorithms with verified invariants and adversarial tests.
-
architecture-decision-recorder — Edition XXII source-attributed supplemental agent procedure: Architecture choice and tradeoff recording.
-
build-reproducibility-receipts — Create verifiable local build and test receipts linking source snapshots, commands and exact artifact bytes.
-
ceta-authority-timeline-autopsy — Reconstruct possible CETA event and authority histories across occurrence, recording, observation, and validity time, and identify distinguishing evidence.
-
ceta-class-router — Choose a Thirstforged Conclave sub-agent class for a CETA task, prepare its bounded assignment and exact skill inventory, and distinguish instruction packets from native profile activation.
-
ceta-cross-representation-meaning-trials — Test whether intent, obligations, schemas, UTF representations, and implementation preserve the same supported meaning, including negative and ambiguous cases.
-
ceta-evidence-cross-examination — Cross-examine a Thirstforged Conclave result against raw observations, exact source bindings, expected predicates, and actual reviewer identity before integration.
-
ceta-frame-authority-confusion — Build bounded TSCG/TSCG-B and policy specimens that separate valid framing and checksums from legitimate actor, scope, freshness, and execution authority.
-
ceta-interrupted-effect-reconstruction — Reconstruct interrupted or cancelled effects from receipts and effect-owner observations, preserving unknown outcomes and preventing unexamined retries.
-
ceta-utf-contract-map — Map a CETA task to the six Universal Thirsty Family tiers and exact isolated Thirsty-Lang 0.9.0 tools, preserving the difference between analysis, integrity, and authority.
-
chronicle-necromancer-decision-history — Recover why a decision changed.
-
chronicle-necromancer-handoff-reconstruction — Find what was lost between people or sessions.
-
chronicle-necromancer-incident-history — Reconstruct a technical incident with uncertain clocks.
-
chronicle-necromancer-message-timeline — Reconstruct events across a message thread.
-
chronicle-necromancer-service-dispute-record — Organize a customer-service record.
-
chronicle-necromancer-version-story — Explain how a document or plan evolved.
-
codex-authority-resolver — Use for resolve governing clause identity and applicable authorization without assuming precedence.
-
codex-autonomy-review — Use for evaluate competence evidence and legitimate authority for autonomy changes.
-
codex-build-reproducer — Use for inventory local build ingredients and reproducibility conditions.
-
codex-claim-integrity — Use for prevent observed/inferred/proposed/implemented states from being conflated.
-
codex-data-lineage — Use for trace source-data provenance and evidence status through transformations.
-
codex-evidence-ledger — Use for validate referenced evidence paths and source identity.
-
codex-failure-reproducer — Use for create reproducibility inputs from logs and source; do not invent successful runs.
-
codex-hostile-review — Use for challenge the implementation for bypass, risk, and missing negative evidence.
-
codex-policy-conflict — Use for preserve conflicting clauses and freeze only affected consequential branches.
-
codex-recovery-rollback — Use for assess rollback artifacts, durable continuity and recovery prerequisites.
-
codex-repo-preservation — Use for protect untracked work, check provenance and refuse destructive cleanup.
-
codex-retirement-check — Use for verify decommission/retirement plans for evidence and retained obligations.
-
codex-runtime-architecture — Use for inspect declared runtime entrypoints, interlocks and operational boundaries.
-
codex-runtime-health — Use for inspect health-related logs and configs as static evidence, not live monitoring.
-
codex-scope-guardian — Use for prevent invented or silently widened objectives and repository scope.
-
codex-source-integrity — Use for check bundled source document checksums and protect observed provenance.
-
conclave-chronicle-necromancer — Retains causal reconstruction and authority timelines, then makes those methods useful for message threads, decision histories, disputes and lost handoffs.
-
conclave-evaluation-lab — Design held-out comparisons of the equipped agent and baseline workflows with matched models, tools, budgets, and recorded evidence.
-
conclave-language-workbench — Use Thirsty-lang as the primary local language and TSCG-B to encode/decode exact UTF-8 task and result text.
-
concurrency-performance-engineer — Implement and measure safe concurrency, latency and memory-budget improvements.
-
epistemic-status-enforcer — Apply explicit epistemic status to meaningful claims.
-
identity-continuity-auditor — Edition XXII source-attributed supplemental agent procedure: Continuity and principal identity auditing.
-
memory-governance-designer — Edition XXII source-attributed supplemental agent procedure: Provenance-first memory rules.
-
polyglot-stack-selector — Select practical combinations of programming languages and runtime boundaries for one application.
-
proof-obligation-generator — Edition XXII source-attributed supplemental agent procedure: Execution proof obligation construction.
-
property-fuzz-test-engineer — Implement executable property-based tests, deterministic fuzz harnesses and failure minimization for source code.
-
python-production-coder — Implement and repair working Python applications, libraries and asynchronous services.
-
rea — Edition XXII source-attributed supplemental agent procedure: REA bounded red-team protocol.
-
state-machine-coder — Implement real finite-state systems, workflows and lifecycle logic with explicit transition guards, invariants and recovery.
-
thirsty-work-orchestrator — Edition XXII source-attributed supplemental agent procedure: Role graph scheduling and evidence handoff.
-
type-contract-architect — Create implementable domain types and API contracts before coding.
Thirsty-lang and TSCG-B in practice
Run the packaged helper with Python 3.10+ to generate a readable result, structured JSON, the executed .thirsty calculation, a binary .tscg-b result and an execution receipt. The helper executes supported arithmetic in Thirsty-lang and independently checks the result; Python handles structured input and the domain algorithm. TSCG-B preserves result text through binary encode/decode. A valid frame does not itself prove the text is true or authorize an action.
Preservation and validation
Every original skill identity and the specialist methods remain, together with the six everyday additions and repaired named dependencies. The Agensi upload layout adapts executable scripts and reference delivery; historical source files and preservation records remain in the creator's original archive.
The repaired collection passed 409 local delivery and execution checks, including all 19 standalone class helpers, real Thirsty-lang calculations, TSCG-B round trips, exact task packets, delivery limits and negative cases. Independent checks also passed all 52 distinct audit-tool bindings and their source-index lookups. Six compiler-specific examples were not executed because their compiler dependencies were absent. These results do not establish every AI host's behavior, marketplace approval, live buyer retrieval, frontier-model superiority or revenue.
Start using it
Connect your AI to Agensi and ask: “Use my Agensi skill 04 — Chronicle Necromancer · Complete Edition. My goal is [result]. Here is my actual material: [notes, records or code].” The pack provides an index; your AI loads the class entrypoint skills/conclave-chronicle-necromancer/SKILL.md, then loads the supporting skills relevant to your task. Purchasing the pack does not automatically run all its skills at once.
Text and reasoning workflows run through your existing AI. Standalone scripts additionally require Python 3.10+ and a code execution tool. Thirsty-lang and TSCG-B execution requires thirsty-lang==0.9.0 installed separately in that environment; your AI should explain missing requirements before starting. Scripts are fetched unchanged through Agensi, executed temporarily and removed. Task result files can be delivered to you; the purchased skill is not installed as a downloadable local folder.
Image, video, voice and data services from Agensi's optional tools catalog are separate paid services. This pack does not require adding those services merely to use its text workflows or Python helpers. External actions, compiler tasks and account access still require the actual relevant host tools and your permission.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Research & Analysis.
This is a skill/class package for an existing compatible AI host. It does not supply model weights, hosted compute, API credits, automatic account connections or permissions. The included helpers accept bounded structured inputs; they are not general document parsers or substitutes for semantic review. Their actual synthetic-fixture outputs are distinguished from authored specialist illustrations. Local preservation/tool checks do not establish correctness on arbitrary tasks, frontier-model superiority, customer results or revenue. Optional UTF analysis features may require additional dependencies. Marketplace ingestion of the final multi-skill ZIP remains subject to the receiving platform’s actual review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
- Software
Node.js
- Optional
Python 3.10+thirsty-lang==0.9.0
Text workflows use your connected AI. Code needs Python 3.10+ and an execution tool. Thirsty-lang and TSCG-B need thirsty-lang==0.9.0 installed in that environment. No hosted model or API credits are included.
Permissions
Read Files, Write Files and Terminal/Shell support the optional local examples and authorized project work. Work stays within the user-approved scope. Browser, network, services and credentials are task-dependent and are not granted by this package. A draft, recommendation or prepared payload is not evidence of an external action.