skills.rest
ehartye
ehartyeCOMMUNITY
Explore all skills by this author →
GitHub

wiki-triage

Presents a browser-based disposition queue for wiki sources needing human review.

Updated Jul 16, 2026
Search Tags:#obsidian#wiki#triage#source management#clipping#disposition#review queue
One-click install
npx skills add https://github.com/ehartye/wiki-master --skill wiki-triage-ehartye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-triage
Source: https://github.com/ehartye/wiki-master/tree/main/skills/wiki-triage
Command: npx skills add https://github.com/ehartye/wiki-master --skill wiki-triage-ehartye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Clipping failures, fidelity flags, expiring declines, and ingest decisions get lost in terminal scrollback; this Skill surfaces every link that needs human judgment in a persistent, token-secured browser queue and records each disposition in an append-only log. ## Core Features & Use Cases - Disposition Queue UI: Launches a local session-token-authenticated web UI grouping issues by kind (failed, thin, fidelity, expiring, backlog) and by research topic. - Disposition Handling: Reads back user decisions from triage.jsonl and acts on them — retrying clips, recording declines, reclipping PDFs/DOCX, quarantining sources, or handing off to ingest. - Manual Queuing: Lets the agent file issues (failed, gone, thin, wrong-node, blocked, fidelity, attention) with topic attribution whenever a run surfaces a link only a human can settle. - Use Case: After a research sweep leaves paywalled pages and gibberish PDFs behind, run the triage queue, hand the user the login link, and apply their dispositions next turn. ## Quick Start Ask the agent to show what wiki sources need attention, then open the provided link to disposition each item in the browser.

Frequently Asked Questions about wiki-triage

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

FAQPage Schema
How do I review failed web clippings in an Obsidian wiki?▼

Run the triage script to start a local queue server, then open the printed link in a browser. The link carries a session token that logs you in once; dispositions are recorded to triage.jsonl and applied by the agent on the next turn.

How do I access the triage queue from another machine?▼

Run the triage script with the --remote flag to bind all interfaces and advertise a reachable address. The same token and link apply, but over a plain LAN the token crosses in cleartext, so use a tailnet or HTTPS front on untrusted networks.

What happens when a source is declined in the triage queue?▼

A decline is recorded with a reason via the clip script and carries a 180-day TTL. Expiring declines resurface for reconsideration, and keep-declined resets the TTL without re-evaluating the source.

Why should transient fetch failures not be marked as declines?▼

A 403 or timeout is a fact about one fetch, while a decline is a judgment with a 180-day TTL. Filing a transient failure as a decline buries a recoverable source; queue it as failed instead so it can be retried.

Can the triage log be edited or rewritten directly?▼

No, triage.jsonl is strictly append-only and state is folded at read time. Two sessions can share one vault, and a read-modify-write would silently lose the other session's entries.

Related Skills

Explore More Education & Research Skills→
Amarbharati-07Amarbharati-07

legal-contract

Draft and review legal documents with plain-language explanations and red-flag checks.

Community
Advanced
LamseyahEliasLamseyahElias

llm-wiki

Create and maintain an interlinked Markdown knowledge base with YAML frontmatter.

Community
Advanced
sanchitnissanchitnis

wiki-lint

Audit Obsidian wikis for broken links, missing frontmatter, and inconsistencies.

Community
Advanced
zvadaadamzvadaadam
47

greenlight-pr

Automates GitHub PR health by triaging CI failures and bot reviews.

Community
Advanced