Knock logo

Knock

Community
Hmbown
knock

Knock is specifically about restoring legitimate access through authorized channels. It is NOT about: - Performance optimization (slow queries, throughput issues) → different spell - Removing safety controls (approval gates, compliance checks) → different spell - Simple bug fixes (typos, wrong ports) → different spell - Breaking constraints (resource limits, CPU throttling) → different spell - Security analysis (encryption schemes, certificate inspection) → different spell

Overview

PublisherHmbown
RepositoryWizards-of-the-Ghosts
Skill nameknock
Stars
106
Forks
10
Bundled files
Instructions only
LicenseCC0-1.0
Links
Skill sourceRepository
  • 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 Knock AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/actions-access-and-automation/knock .claude/skills/knock
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

Knock

Bypass access friction through legitimate unlock paths: key rotation, permission requests, and recovery workflows.

What This Skill Does

Knock is specifically about restoring legitimate access through authorized channels. It is NOT about: - Performance optimization (slow queries, throughput issues) → different spell

  • Removing safety controls (approval gates, compliance checks) → different spell
  • Simple bug fixes (typos, wrong ports) → different spell
  • Breaking constraints (resource limits, CPU throttling) → different spell
  • Security analysis (encryption schemes, certificate inspection) → different spell In this grimoire, Knock is treated as a literal spell with a prototype delivery profile. Canonical reference input: Knock (spell).

When To Use

  • Activate this spell when the user's request contains an access barrier with a legitimate recovery path. Look for these patterns:
  • Expired/rotated credentials: "credentials expired", "token revoked", "certificate expired", "password rotated", "key expired"
  • Locked resources: "lockfile", "state is locked", "DynamoDB lock", "stale lock"
  • Permission gaps: "locked out", "permissions removed", "RBAC", "403", "unauthorized", "access denied"
  • Blocked processes: "stuck behind", "can't authenticate", "connection rejected", "sealed" (Vault)
  • Recovery language: "rotate", "renew", "unseal", "reinstate", "force-unlock", "exception request", "proper channel"
  • The core signal: something is blocking access, and there exists an authorized way to restore it.

Prerequisites

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

Procedure

  1. Restate the target, the success condition, and any no-touch boundaries before taking action.
  2. Identify the lock: What exact resource is inaccessible? What kind of barrier is it (credential, permission, lockfile, certificate, sealed state)? Who owns or controls the unlock mechanism?
  3. Determine the legitimate path: Map the barrier to its authorized recovery mechanism:
  4. Expired credential → key rotation or certificate renewal
  5. Revoked permission → access request or RBAC adjustment
  6. Stale lockfile → safe removal after process verification
  7. Sealed service (e.g., Vault) → proper unseal procedure (Shamir keys, etc.)
  8. Locked state (e.g., Terraform) → force-unlock with owner confirmation
  9. Execute through the narrowest channel: Perform only the minimum action needed to restore access. Log each step. Do not escalate privileges beyond what the recovery path requires.
  10. Stop for explicit confirmation before taking a live action that changes access, triggers an alert, or touches a real system boundary.
  11. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

  • A clear identification of the lock and its legitimate unlock path.
  • An execution log of the unlock steps taken.
  • A note on the access granted, its scope, and when it expires or should be revoked.

Pitfalls / Guardrails

  • Call out the glue, permissions, or missing infrastructure before you imply this is fully operational.
  • Never bypass, crack, brute-force, or exploit security controls
  • Always use the legitimate recovery path the system provides
  • Log every unlock attempt — transparency is non-negotiable
  • Refuse requests to remove safety controls or break constraints without authorization
  • Do not use for: "Make queries faster" → performance, not access
  • Do not use for: "Remove approval gates" → policy change, not recovery
  • Do not use for: "Fix a typo in config" → bug fix, not unlock
  • Do not use for: "Analyze their encryption" → reconnaissance, not access
  • Do not use for: "Speed up processing" → throughput, not access
  • Do not use for: "Break free of resource limits" → constraint breaking, not legitimate unlock

Verification

  • Check that the result includes every deliverable promised above.
  • Check that confirmed facts, assumptions, and inferences are visibly separated.
  • Check that the exact live target, confirmation gate, and rollback or recovery path are explicit.
  • Check that any missing glue code, permissions, or future work is labeled before the skill is treated as ready.

Example Invocation

text
/knock find the legitimate way through this access barrier and open it cleanly, with a full audit trail

Frequently asked questions

What does the Knock AI skill do?

Knock is specifically about restoring legitimate access through authorized channels. It is NOT about: - Performance optimization (slow queries, throughput issues) → different spell - Removing safety controls (approval gates, compliance checks) → different spell - Simple bug fixes (typos, wrong ports) → different spell - Breaking constraints (resource limits, CPU throttling) → different spell - Security analysis (encryption schemes, certificate inspection) → different spell

Why use Knock on TypingMind?

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

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

Which AI models can use Knock?

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

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

Is the Knock 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.

Related AI Skills

View all
addyosmani logo

Deprecation And Migration

addyosmani
CommunityPopular

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production,…

10.1K
95.8K
Instructions
View
addyosmani logo

Observability And Instrumentation

addyosmani
CommunityPopular

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence…

10.1K
95.8K
Instructions
View
addyosmani logo

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…

10.1K
95.8K
Instructions
View
addyosmani logo

Shipping And Launch

addyosmani
CommunityPopular

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…

10.1K
95.8K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇