Openhound Development

Organization

SpecterOps

openhound-development

Use for OpenHound collector and OpenGraph extension development work, including planning, graph schema, source collection, assets, lookup/preproc, registration, validation, and collector template adaptation under the BloodHound plugin.

Overview

Publisher	SpecterOps
Repository	`skills`
Skill name	`openhound-development`
Stars	706
Forks	80
Bundled files	10
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
10 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by SpecterOps on GitHub. Read the source before you install it.

Installation

Install the Openhound Development AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/SpecterOps/skills/tree/main/plugins/bloodhound/skills/openhound-development
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/SpecterOps/skills/tree/main/plugins/bloodhound/skills/openhound-development

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/SpecterOps/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/plugins/bloodhound/skills/openhound-development .claude/skills/openhound-development

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Openhound Development in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Openhound Development on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Openhound Development is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OpenHound Development

Use this skill for any OpenHound collector task.

Critical Rules (Always apply)

Read ../../standards/openhound/openhound.md before editing collector code when working from this plugin, or .agents/standards/openhound.md inside a generated collector repo. This includes important standards and best practices for OpenHound collector development that are not repeated in the reference docs.
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.
For broad collector work, or when creating a new collector, read ../../standards/openhound/workflow.md when working from this plugin, or .agents/standards/workflow.md inside a generated collector repo.
Important: Before finishing collector and graph behavior changes read references/validate-extension.md.

Route By Task

Task	Reference
Plan a new collector from API docs, sample responses, or requirements	`references/plan-collector.md`
Define graph base classes, common properties, node IDs, or edge properties	`references/graph-schema.md`
Register `collect`, `preproc`, `convert`, metadata, or entry points	`references/register-extension.md`
Implement API clients, auth, DLT resources, transformers, or secrets	`references/source-collection.md`
Add or modify models, node assets, edge assets, kind constants, or exports	`references/add-asset.md`
Add DuckDB transforms, lookup methods, lookup registration, or `self._lookup` usage	`references/preproc-lookup.md`
Validate collector changes before finishing	`references/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 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Openhound Development AI skill do?

Why use Openhound Development on TypingMind?

Because you install it once and use it with any model. Openhound Development is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Openhound Development in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/SpecterOps/skills/tree/main/plugins/bloodhound/skills/openhound-development. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Openhound Development?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Openhound Development?

As many as you like. As long as a model supports skills, you can use Openhound Development with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Openhound Development AI skill free?

Yes. It is published on GitHub by SpecterOps under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mcp Dependency Review

affaan-m

CommunityPopular

Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or…

Skill Host Compat

Lint ECC skills for Codex/Cursor-safe frontmatter and Claude-only substitutions before a skill PR.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Bun Runtime

Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OpenHound Development

Critical Rules (Always apply)

Route By Task

Routing Rules

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now