Identify

Community

Hmbown

identify

Overview

Publisher	Hmbown
Repository	`Wizards-of-the-Ghosts`
Skill name	`identify`
Stars	106
Forks	10
Bundled files	Instructions only
License	CC0-1.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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Hmbown on GitHub. Read the source before you install it.

Installation

Install the Identify 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.
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/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/investigation-and-preparation/identify

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/Hmbown/Wizards-of-the-Ghosts.git /tmp/Wizards-of-the-Ghosts
mkdir -p .claude/skills
cp -r /tmp/Wizards-of-the-Ghosts/generated/hermes/investigation-and-preparation/identify .claude/skills/identify

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

Use it in TypingMind

Enable Identify 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 Identify 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 Identify 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.

Identify

Explain what a mysterious file, service, workflow, or artifact actually does.

What This Skill Does

Identify is static analysis for operational understanding. It answers "What is this?" by inspecting structure, naming, dependencies, and runtime touchpoints. It does NOT search for artifacts, debug failures, monitor systems, verify claims, or modify code. In this grimoire, Identify is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Identify (spell).

When To Use

Use this spell when a user presents a specific artifact (file, script, config, service, binary, module, chart, extension, etc.) and asks any variation of:
"What does this do?"
"Explain this [artifact]"
"What is this for?"
"What does it touch/depend on?"
"What can we prove from inspection?"
"What's the safest next validation step?"
Key signal: The artifact is already in hand. The question is about understanding, not finding, fixing, watching, or changing it.

Prerequisites

No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

Procedure

Restate the target, the success condition, and any no-touch boundaries before taking action.
Restate boundaries: Name the target, the success condition, and any no-touch constraints before acting.
Inspect directly: Read the artifact's contents. Do not speculate before looking.
Infer from evidence: Determine purpose from structure, dependencies, naming conventions, and runtime touchpoints (ports, volumes, secrets, APIs, services).
Separate certainty levels: Classify findings as:
Confirmed (directly visible in the artifact)
Likely (strong inference from patterns/contexts)
Unknown (cannot be proven without runtime testing or external data)
Return structured output: Provide:
Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

A plain-English explanation of the artifact.
Inputs, outputs, dependencies, and side effects when known.
A confidence-rated list of unknowns.

Pitfalls / Guardrails

Keep the metaphor anchored to a real mechanism instead of drifting into lore.
Never overstate certainty when runtime behavior cannot be validated statically.
Prefer source-backed explanation over assumptions or lore.
If the user asks you to modify the artifact after identifying it, complete the Identify workflow first, then switch to the appropriate editing spell.
Do not use for: "Find where X is defined" → Use search/locate, not Identify
Do not use for: "Why did this break?" or "Trace the root cause" → Use debugging/incident response
Do not use for: "Watch this system for changes" → Use monitoring/observability
Do not use for: "Compare these claims against the code" → Use verification/audit
Do not use for: "Change/modify/update this" → Use editing/transformation spells

Verification

Check that the result includes every deliverable promised above.
Check that confirmed facts, assumptions, and inferences are visibly separated.
Check that the metaphor still maps cleanly to a real operational mechanism.

Example Invocation

text
/identify Use $identify on this file, tool, or service and tell me what it does, what it touches, and what we still do not know

Frequently asked questions

What does the Identify AI skill do?

Why use Identify on TypingMind?

Because you install it once and use it with any model. Identify 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 Identify in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/investigation-and-preparation/identify. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Identify?

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 Identify?

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

Is the Identify AI skill free?

Yes. It is published on GitHub by Hmbown under the CC0-1.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

Performance Optimization

addyosmani

CommunityPopular

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load…

Shipping And Launch

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up…

Using Agent Skills

Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all…

Ruview Applications

Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Identify

What This Skill Does

When To Use

Prerequisites

Procedure

Deliverables

Pitfalls / Guardrails

Verification

Example Invocation

Frequently asked questions

Related AI Skills

Set up your own AI workspace now