chronicle-delete-asset

Permanently deletes orphaned Chronicle assets not linked to any experiment.

1|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/methodic-research/skills --skill chronicle-delete-asset-methodic-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chronicle-delete-asset
Source: https://github.com/methodic-research/skills/tree/main/plugins/chronicle/skills/delete-asset
Command: npx skills add https://github.com/methodic-research/skills --skill chronicle-delete-asset-methodic-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research platforms accumulate orphaned uploads — duplicate datasets, abandoned pending uploads, files uploaded by mistake — that clutter storage and search results. This Skill permanently removes those unlinked Chronicle assets while protecting anything still referenced by an experiment record. ## Core Features & Use Cases - Guarded hard delete: Calls the bundled chronicle.delete_asset MCP tool, which transactionally removes the asset row, ACLs, and inline content, then purges storage bytes and search documents best-effort. - Linked-asset protection: The server refuses deletion with a 409 (including per-table link counts) when an asset is referenced by any experiment, variation, or output — those assets are governed by deprecate/invalidate instead. - Confirmation-first workflow: Always previews the exact asset list and requires explicit user confirmation before the irreversible delete. - Use Case: After deleting a draft experiment, its formerly linked datasets become orphans; use this Skill to clean them up, sorting outcomes into deleted, linked-skipped, already-gone, and failed. ## Quick Start Ask the agent to permanently delete the orphaned Chronicle assets with these ids, confirming the previewed list before the irreversible deletion proceeds.

Frequently Asked Questions about chronicle-delete-asset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delete orphaned assets in Chronicle?▼

Provide the asset UUIDs, review the previewed list of names, types, and states, then explicitly confirm. The skill calls the chronicle.delete_asset MCP tool for each id, which removes the row, ACLs, inline content, storage bytes, and search document.

Why does Chronicle refuse to delete my asset with a 409 error?▼

A 409 means the asset is still linked as an experiment, variation, or output input/output, and linked assets are part of the research record. Use chronicle.assets.invalidate or chronicle.assets.deprecate instead, or delete the linking draft experiment first.

Do I need to install the methodic SDK to delete Chronicle assets?▼

No, the delete itself uses the bundled chronicle.delete_asset MCP tool with no pip install. The SDK is only needed for the optional metadata preview (chronicle.assets.get) and the deprecate/invalidate alternatives, which have no MCP tool.

What is the difference between deleting, deprecating, and invalidating a Chronicle asset?▼

Delete permanently removes an unlinked asset and its storage. Deprecate adds a soft warning while keeping it usable, and invalidate hard-blocks it as an input; both preserve the row and provenance for linked assets.

Can I recover a Chronicle asset after hard deletion?▼

No, hard delete is irreversible — the asset row, ACLs, inline content, and storage bytes are removed. That is why the skill always shows the concrete asset list and requires explicit confirmation before proceeding.