Texarkanine
- 24 skills
- 0 followers
- last month last updated
- ▌ Sr Semantic · texarkanineMeaning-based (vector) search over your local warehouse of agentic-coding history. Reach for this when the question is about content or concepts you can describe but not name exactly — "conversations about flaky tests", "where did we debug the deadlock" — not exact ids, filters, or counts (that is sr-query).
- ▌ Sr Dashboard · texarkanineOpen the local stockroom dashboard — a read-only, fully offline at-a-glance view of cross-harness agentic-coding history. Reach for this when you (or the user) want the metrics UI URL, not SQL or semantic search.
- ▌ Sr Initialize · texarkanineSet up stockroom on this machine — check prerequisites, provision the per-machine torch build, smoke-test the embedding path, put the `stockroom` command on PATH, schedule the nightly ingest+embed, and run the first full ingest. Run this on a new machine, after a "run sr-initialize" error from a sibling skill, or any time the setup seems broken; it re-probes and only does what is still missing.
- ▌ Sr Query · texarkanine bundleRun read-only SQL against your local warehouse of agentic-coding history (sessions, messages, tool calls, embeddings). Reach for this on exact or structured lookups — known ids, WHERE filters, counts, GROUP BY, joins, aggregations — not meaning-based search (that is sr-semantic).
- ▌ Sr Search · texarkanine bundleSearch your local warehouse of agentic-coding history — the friendly default entrypoint. Reach for this when you are unsure whether the question is an exact/structured lookup (sr-query) or meaning-based recall (sr-semantic), or when it needs both — it routes the question, runs the right surface(s), and synthesizes one answer.
- ▌
- ▌ Niko Preflight 2 · texarkanineNiko Memory Bank System - Preflight Phase - Pre-Build Plan Validation
- ▌ Slobac Audit · texarkanine bundleUse this skill to audit a test suite or set of test files for for test quality and design smells. Produces a portable findings report without modifying code.
- ▌ Visual Planning · texarkanineGuidelines for using Mermaid diagrams to increase comprehension of complex processes. Apply when planning non-trivial work involving multiple components, interactions, data models, or process flows, or when describing a system with complex interactions where prose alone becomes unwieldy.
- ▌
- ▌
- ▌ Shell Posix Style · texarkanineRequired style guidelines for writing shell scripts where POSIX-compliance is REQUIRED
- ▌ Illustrate Complexity · texarkanineDecide whether an explanation needs a diagram, pick the right Mermaid type, and write it so it renders. Use when explaining a system's structure, flow, or relationships - in docs, READMEs, design notes, prompts, plans, or a chat answer - even when nobody asked for a diagram. Not for charting numeric data.
- ▌
- ▌ Nk Refresh · texarkanineGeneral-purpose guidance for taking a step back and getting un-stuck from a problem that you've tried to solve multiple times unsuccessfully.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Bash Style · texarkanineRequired style guidelines for writing shell scripts where POSIX-compliance is not an explicit requirement
- ▌
- ▌