agentleFS
Sign inStart free
d3vzer0d3vzer0/agent-skills/skills/openhound/SKILL.md

openhound

Skill1 starsChanged 4 months agoMITView on GitHub

Use for all OpenHound collector work, including planning, graph schema, source collection, assets, lookup/preproc, registration, and validation.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for any OpenHound collector task.

    line 8
  2. Very specific:

    Read references/architecture.md before editing collector code.

    line 13
  3. Distinctive:

    If the task touches multiple areas, read every matching reference.

    line 33
  4. Very specific:

    If adding or changing collector behavior, always read references/validate-extension.md before finishing.

    line 34
  5. Very specific:

    If the task involves a new collector or broad redesign, start with references/plan-collector.md.

    line 35
  6. Very specific:

    If a collector supports more than one authentication method, read references/multi-auth.md and references/source-collection.md.

    line 36
  7. Very specific:

    If models use self._lookup, also read references/preproc-lookup.md and references/register-extension.md.

    line 37
  8. Very specific:

    If adding a new collected resource, usually read references/source-collection.md, references/add-asset.md, and …

    line 38

≈ “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

OpenHound Development Skill

Use this skill for any OpenHound collector task.

Critical Rules (Always apply)

  1. Read references/architecture.md before editing collector code. This includes important standards and best practices for OpenHound collector development that are not repeated in the reference docs.
  2. Based on the requested task, select the matching reference from the routing table. These contain specific rules and examples for different types of collector work.
  3. For broad collector work, or when creating a new collector, read references/plan-collector.md.
  4. Important: Before finishing collector and graph behavior changes read references/validate-extension.md.

Route By Task

TaskReference
Plan a new collector from API docs, sample responses, or requirementsreferences/plan-collector.md
Define graph base classes, common properties, node IDs, or edge propertiesreferences/graph-schema.md
Register collect, preproc, convert, metadata, or entry pointsreferences/register-extension.md
Implement API clients, auth, DLT resources, transformers, or secretsreferences/source-collection.md
Implement multiple authentication options with DLT configspec unionsreferences/multi-auth.md
Add or modify models, node assets, edge assets, kind constants, or exportsreferences/add-asset.md
Add DuckDB transforms, lookup methods, lookup registration, or self._lookup usagereferences/preproc-lookup.md
Validate collector changes before finishingreferences/validate-extension.md

Routing Rules

  • If the task touches multiple areas, read every matching reference.
  • If adding or changing collector behavior, always read references/validate-extension.md before finishing.
  • If the task involves a new collector or broad redesign, start with references/plan-collector.md.
  • If a collector supports more than one authentication method, read references/multi-auth.md and references/source-collection.md.
  • If models use self._lookup, also read references/preproc-lookup.md and references/register-extension.md.
  • If adding a new collected resource, usually read references/source-collection.md, references/add-asset.md, and references/validate-extension.md.

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