Records and searches expensive dead ends in a git-committed append-only ledger.
npx skills add https://github.com/vinzenz/workflows --skill tried-vinzenz
Please help me install this Agent Skill. Skill: tried Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/tried Command: npx skills add https://github.com/vinzenz/workflows --skill tried-vinzenz
.tried/ledger.md, committed alongside the code. - Cheap search before work: tried search matches queries against approach, reason, and topic so an agent can check for known dead ends before spending time. - Idempotent, concurrent-safe writes: Entries are content-hashed so identical records are not duplicated, and appends use a single O_APPEND write so parallel agents do not corrupt the file. - Use Case: Before re-architecting token refresh logic, run tried search "rotate refresh tokens" and discover a prior entry explaining the replay-window race that made it fail. ## Quick Start Ask the agent to check the tried ledger for previous attempts at your planned approach before starting work on it.High-intent search queries and answers about installing and using this skill.
Run `tried search "<query>"` to match words against recorded approaches, reasons, and topics. Start with a bare `tried` invocation for recent entries and the busiest topics, then use `tried show <id>` for a full entry.
Use `tried add "<approach>" --verdict failed --topic <topic> --because "<reason>"`. The verdict must be one of failed, abandoned, worked, or partial, and the reason is required. Use `--dry-run` to preview without writing.
tried is a curated, structured, git-committed ledger of verdicts on specific approaches that travels with the repository. agent-log is an unstructured, machine-local transcript index of everything every session did, rebuilt automatically and not committed.
Yes. The ledger lives at `.tried/ledger.md` in the repository and is committed alongside the code, so it travels with clones, pull requests, and different machines. You can override the location with the TRIED_LEDGER environment variable.
Appends use a single O_APPEND write, so concurrent adds land sequentially without corrupting the file. Identical content is detected via content hashing and reported as already_recorded rather than duplicated.
Do not log routine steps, first-try failures, or trivial mistakes. The ledger only stays useful if it remains sparse; an approach should have cost real time, roughly more than fifteen minutes or repeated failed attempts, before it qualifies.
DieStokSearch and summarize coding agent session history from logs and metadata.
withmartian-sandbox-darksideCreate or update continuity ledgers to preserve session state across /clear operations.
nq-rdlSearch JSONL agent session logs with DuckDB queries to recover past decisions.
AnasIsmai1Shapes raw markdown material into a structured article through paragraph-by-paragraph drafting.