hraness

hraness

@hraness Organization

GitHub
12 Skills
0 Total Stars
October 2026 Joined

Public Skills

ghostget

by hraness

Use GhostGet for named web actions: capture public or signed-in pages as Markdown; archive authorized audio, video, and transcripts with verification; query encrypted cached email, contacts, inboxes, and messages; resolve live conversations, read fresh context, preview message bubbles, and send owner-confirmed turns through one provider route; publish and reconcile text, image, and video posts through reviewed routes; save private native article drafts; and build or run typed contracts and plugins for X, LinkedIn, Bluesky, Substack Notes, Threads, TikTok, Instagram, and YouTube Shorts from recorded browser APIs or versioned CLIs. Covers Beeper messaging across the pinned official CLI and fixed Desktop loopback operations. Trigger for scraping, URL clipping, authenticated sites, media downloads, transcription, email and messaging, cross-posting, HAR-to-API workflows, browser-session API automation, semantic operations, and confirmed writes. Named actions never expose raw HTTP, DOM, cookies, or credentials.

API Dev 0 19d ago

save-pdf-kb

by hraness

Convert a local or public remote PDF into an auditable Markdown knowledge-base bundle with the original document, inferred headings, page provenance, OCR text, image metadata, and local visual assets. Use when the user asks to save, import, archive, extract, or turn a PDF into KB Markdown, especially scanned documents and PDFs containing screenshots, Slack messages, charts, photos, or a mix of native text and images.

Code Review 0 26d ago

refresh-kb

by hraness

Refresh and validate a hraness/wordcell Markdown knowledge graph after notes, concepts, typed relationships, attachments, repository scopes, or context mappings change. Use when an agent needs to maintain a managed or authored catalog, inspect graph and lifecycle findings, validate local artifacts and scope hubs, or complete a vault health check.

CLI Tools 0 26d ago

plan-kb

by hraness

Create or evolve a durable Markdown plan inside a hraness/wordcell vault. Use when a user asks for an implementation plan, proposal, RFC, migration plan, execution audit, phased checklist, or an update to an existing plan's decisions, progress, review findings, verification evidence, or final result.

Code Review 0 26d ago

percolate-kb

by hraness

Review a hraness/wordcell Markdown vault for recurring ideas and missing structural connections, then promote evidence-backed concepts and typed relationships with the Wordcell CLI. Use after materially adding or revising notes, when organizing an accumulated vault, or when an agent needs to turn repeated tags and prose references into an explicit queryable knowledge graph.

Code Gen 0 26d ago

save-url-kb

by hraness

Capture public or signed-in web content into a local Markdown knowledge base as an auditable source bundle with local assets. Use when the user asks to clip, save, scrape, or archive an article, social post or thread, GitHub or Discourse discussion, feed, inbox, private document, WhatsApp conversation, YouTube page, or another page already visible in their browser. Supports URL capture, the current signed-in tab, temporary browser-profile snapshots, saved HTML, media, evidence, honest completeness, and knowledge-base linking.

Code Review 0 26d ago

query-kb

by hraness

Load scoped repository context, then search and navigate a hraness/wordcell Markdown vault with hybrid text retrieval, exact metadata, bounded links and typed relationships, backlinks, whole-vault graph reports, and optional Git provenance. Use when an agent needs the applicable repository instructions, rationale, prior knowledge, plans, captures, decisions, concepts, relationships, or evidence before answering, planning, or changing code.

Code Review 0 26d ago

phase-reviewer

by hraness

Reviews and fixes a just-implemented phase of a multi-phase plan during a phase-orchestrator run. Use after a phase's implementation and initial validation: checks the phase against the plan, PRD/spec, repo conventions, security, tenancy/data ownership, migrations, and test coverage, and patches bounded low-risk issues directly. Never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.

Code Review 0 1mo ago

phase-final-reviewer

by hraness

End-to-end reviewer for a completed multi-phase feature at the end of a phase-orchestrator run. Use after all requested phases are finalized: inspects the whole feature against the plan and PRD/spec, hunting integration bugs across phase boundaries, missing acceptance criteria, stale plan state, and validation gaps. Patches only safe concrete issues; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.

Code Review 0 1mo ago

phase-orchestrator

by hraness

Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes plans in the write-phase-plan format. Use when the user provides a plan, checklist, PRD, or phase document and asks for delegated multi-agent execution across phases.

Code Review 0 1mo ago

phase-implementer

by hraness

Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them.

Code Review 0 1mo ago

write-phase-plan

by hraness

Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration, prepare a plan or PRD for delegated multi-agent implementation, or convert a spec, checklist, or design doc into implementable phases.

Code Review 0 1mo ago