agentleFS
Sign inStart free
r0shir0shi/harborclerk/skills/harbor-clerk/SKILL.md

harbor-clerk

Skill3 starsChanged 31 days agoMITView on GitHub

Search and read documents from a local Harbor Clerk knowledge base. Use when the user references their personal documents, contracts, notes, emails, or asks "what did I store about X?

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run harbor-clerk --help for the full command list, then harbor-clerk <cmd> --help for any specific command.

    line 11
  2. Very specific:

    Search returns top-level .hits[].

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Harbor Clerk - extended memory for agents

Harbor Clerk is a local document corpus with hybrid FTS+vector search and citation-ready reads. This skill exposes it via the harbor-clerk CLI.

First step: discover the surface

Run harbor-clerk --help for the full command list, then harbor-clerk <cmd> --help for any specific command. The help is comprehensive: JSON return shapes, examples, and common mistakes are all there.

Four patterns you'll use most

  1. Search → expand: harbor-clerk search "..." then harbor-clerk expand-context <chunk_id> -n 3 on the best hit.
  2. Find every matching document: harbor-clerk find-all "..." --text-contains "literal phrase" --presentation full when the task asks to list or enumerate.
  3. Read a known document: harbor-clerk read-document <doc_id> for full text with pagination.
  4. Check ingest status before searching for new content: harbor-clerk ingest-status <doc_id> returns per-stage state.

What you can trust

  • Search returns top-level .hits[]; Find All returns top-level .results[]. Result-bearing commands include source, citation, and chunk_id when available. Use those fields as the citation trail, then call read-passages when you need exact surrounding text.
  • possible_conflict: true means top hits span multiple similarly scored documents; inspect the relevant sources before answering.
  • ingest-status, read-document, and entity commands may require a Full-tier API key. If access is denied, continue with search and passage reads, and tell the user the key may be scoped too narrowly for that command.
  • The CLI exits non-zero on failure. Exit code 3 specifically means an admin has disabled CLI access; tell the user.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free