- Home
- Skills
- Productivity
- 14 — Obligation Revenant · Complete Edition
Works with the AI Agents you already use
14 — Obligation Revenant · Complete Edition
Keeps residual-obligation reconciliation and uncertain-effect handling, adding project restarts, promise ledgers, session recovery and reliable handoffs.
$25
14 — Obligation Revenant · Complete Edition
Example session with this skill installed
Everyday request
I left this project for three weeks. Here are the notes and files. Tell me what is really finished, what is still owed, and how to restart.
For a reproducible local example, use the included synthetic structured fixture:
{
"tasks": [
{
"id": "research",
"status": "done",
"evidence": "notes-v2"
},
{
"id": "draft",
"status": "open",
"depends_on": [
"research"
]
},
{
"id": "review",
"status": "done"
},
{
"id": "upload",
"status": "unknown_commitment"
}
]
}
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
Obligation Revenant — 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
Restart account:
- research: done
- draft: open
- review: needs_verification
- upload: unknown_commitment
Ready to plan: draft
Reconcile before retrying: upload
A previous done label without evidence does not establish completion; this tool does not dispatch work
Complete structured result
{
"boundary": "A previous done label without evidence does not establish completion; this tool does not dispatch work",
"ready_to_plan": [
"draft"
],
"reconciliation_required": [
"upload"
],
"task_account": [
{
"depends_on": [],
"evidence": "notes-v2",
"id": "research",
"status": "done"
},
{
"depends_on": [
"research"
],
"evidence": null,
"id": "draft",
"status": "open"
},
{
"depends_on": [],
"evidence": null,
"id": "review",
"status": "needs_verification"
},
{
"depends_on": [],
"evidence": null,
"id": "upload",
"status": "unknown_commitment"
}
]
}
Executed Thirsty-lang calculation
module conclave: core
drink result = 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: Resume a project where research has evidence, the draft is open, review was marked done without evidence, and an upload has an uncertain outcome.
Illustrative specialist response: Research remains complete subject to its evidence. The draft is ready to plan because its research prerequisite is met. Review needs verification because a done label is unsupported. The uncertain upload requires reconciliation before retry. The restart brief carries forward the original commitments, preserves blocked and cancelled scope, and distinguishes historical completion from conditions that may have expired.
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
Obligation Revenant — Complete Edition
Bring unfinished work back with its commitments intact.
Keeps residual-obligation reconciliation and uncertain-effect handling, adding project restarts, promise ledgers, session recovery and reliable handoffs.
One class. 47 equipped skills. The original specialist method plus six practical everyday workflows. $25 as a one-time purchase.
For stalled projects, interrupted sessions, half-finished plans and overdue commitments. For deeper work, the class retains its original specialist equipment and source-defined method: What work is still owed, under the currently valid authority?
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
- Verify the source chain and choose a consistent observation cut; retain histories that cannot be ordered.
- Re-evaluate every obligation against its own evidence predicate; never use a previous summary as proof.
- Separate historical fulfillment from predicates that must still hold at resumption time.
- Place unknown commitments in reconciliation-required state and exclude them from dispatch.
- Compute residual obligations and their dependencies; retain blocked, deferred and cancelled scope explicitly.
- Propose a resumption contract that references the original task and exact missing authority.
- Have the owner approve any changed scope; schedule only actions covered by current grants.
Specialist deliverable: resumption_contract. Its source-defined result fields are residual_obligations, satisfied_obligations, stale_evidence, unsettled_operations, required_authority, resume_dependencies. 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. Restart a project that lost momentum
Rebuild the original goal and commitments from supplied sources. Verify completion evidence, identify stale prerequisites and produce the next small milestone.
2. Continue work after a break without losing the task
Carry forward exact constraints and pending decisions. Mark prior claims of completion as claims until their evidence is checked.
3. Recover commitments buried in notes or messages
Extract who explicitly promised what and when. Keep suggestions and hopes separate from commitments, and draft follow-ups without sending.
4. Find what remains behind an almost-finished label
Compare promised deliverables to actual artifacts and acceptance evidence. List the exact finishing work rather than restarting completed parts.
5. Recheck the facts that may have expired
Distinguish historical completion from conditions that must still hold today, such as a current version, permission or deadline.
6. Give someone a reliable restart brief
Summarize the original task, verified work, residual obligations, blockers and uncertainty. Exclude unresolved commitments from automatic retry.
Example 1 — what a specialist assignment can look like
You ask: Resume a project where research has evidence, the draft is open, review was marked done without evidence, and an upload has an uncertain outcome.
Illustrative response: Research remains complete subject to its evidence. The draft is ready to plan because its research prerequisite is met. Review needs verification because a done label is unsupported. The uncertain upload requires reconciliation before retry. The restart brief carries forward the original commitments, preserves blocked and cancelled scope, and distinguishes historical completion from conditions that may have expired.
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
I left this project for three weeks. Here are the notes and files. Tell me what is really finished, what is still owed, and how to restart.
The work product: An evidence-backed status account, remaining commitments, uncertain effects, and a practical restart brief.
The included local helper demonstrates a bounded part of this workflow. Its actual run on synthetic structured input produced:
Restart account:
- research: done
- draft: open
- review: needs_verification
- upload: unknown_commitment
Ready to plan: draft
Reconcile before retrying: upload
A previous done label without evidence does not establish completion; this tool does not dispatch work
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 Obligation Revenant — 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: An evidence-backed status account, remaining commitments, uncertain effects, and a practical restart brief.
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)
-
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-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-intent-obligation-compiler — Turn a user's CETA request into traceable supported obligations while retaining exclusions, corrections, authority boundaries, ambiguity, and unresolved meaning.
-
ceta-interrupted-effect-reconstruction — Reconstruct interrupted or cancelled effects from receipts and effect-owner observations, preserving unknown outcomes and preventing unexamined retries.
-
ceta-resource-pressure-reduction — Minimize a discovered fault or resource-pressure failure into a reproducible causal case while preserving measurement provenance and uncertainty.
-
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.
-
codex-acceptance-crosswalk — Use for map source-defined requirements to executable acceptance evidence.
-
codex-api-contract-auditor — Use for inspect api definition documents, json contracts and documentation consistency.
-
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-dependency-mapper — Use for inspect dependency and integration surfaces with scoped evidence.
-
codex-evidence-ledger — Use for validate referenced evidence paths and source identity.
-
codex-hostile-review — Use for challenge the implementation for bypass, risk, and missing negative evidence.
-
codex-identity-verifier — Use for review verified identity boundary instead of treating familiarity as authentication.
-
codex-operations-support — Use for diagnose support cases using actual logs and local help documentation.
-
codex-owner-decision — Use for prepare and verify actual owner decisions, never invent approval.
-
codex-policy-conflict — Use for preserve conflicting clauses and freeze only affected consequential branches.
-
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.
-
codex-standards-conflict — Use for report contradictory standards and require evidenced precedence.
-
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.
-
conclave-obligation-revenant — Keeps residual-obligation reconciliation and uncertain-effect handling, adding project restarts, promise ledgers, session recovery and reliable handoffs.
-
epistemic-status-enforcer — Apply explicit epistemic status to meaningful claims.
-
obligation-revenant-almost-done-audit — Find what remains behind an almost-finished label.
-
obligation-revenant-project-resurrection — Restart a project that lost momentum.
-
obligation-revenant-promise-ledger — Recover commitments buried in notes or messages.
-
obligation-revenant-restart-handoff — Give someone a reliable restart brief.
-
obligation-revenant-session-resume — Continue work after a break without losing the task.
-
obligation-revenant-stale-evidence-reset — Recheck the facts that may have expired.
-
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.
-
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 14 — Obligation Revenant · 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-obligation-revenant/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 Productivity.
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.