Core Protocols

Community

Aedelon

core-protocols

Debug errors systematically by searching first, then analyzing, then proposing verified solutions. MUST BE USED when user reports: "error", "bug", "doesn't work", "fails", "crash", stack traces, exception messages, or any troubleshooting scenario. Triggers: "TypeError", "ImportError", "undefined is not a function", "segfault", "panic", "broken", "not working", "unexpected behavior", "regression", "failing", "exception", "traceback", "stack trace", "debug this", "why does this fail", "help me fix". Also enforces confidence levels and output templates. Prevents guessing solutions without research.

Overview

Publisher	Aedelon
Repository	`claude-code-blueprint`
Skill name	`core-protocols`
Stars	119
Forks	34
Bundled files	Instructions only
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 Aedelon on GitHub. Read the source before you install it.

Installation

Install the Core Protocols 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/Aedelon/claude-code-blueprint/tree/main/skills/core-protocols
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.

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/Aedelon/claude-code-blueprint.git /tmp/claude-code-blueprint
mkdir -p .claude/skills
cp -r /tmp/claude-code-blueprint/skills/core-protocols .claude/skills/core-protocols

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

Use it in TypingMind

Enable Core Protocols 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 Core Protocols 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 Core Protocols 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.

Core Protocols

1. Debugging Protocol

Trigger Conditions

Activate when:

User reports an error or bug
Code doesn't work as expected
Build/test failures occur
Stack traces or error messages appear

MANDATORY Sequence

NEVER propose solutions before completing Steps 1-2.

Step 1: SEARCH FIRST


1. Extract EXACT error message
2. WebSearch: "[error message] [language/framework] [version]"
3. Context7 if library-related:
   - mcp__context7__resolve-library-id(libraryName)
   - mcp__context7__get-library-docs(id, topic: "error")
4. Look for GitHub issues / StackOverflow

Step 2: ANALYZE


1. Identify ROOT CAUSE (not symptoms)
2. Check version compatibility
3. Isolate the problem
4. Check changelogs for breaking changes

Step 3: VERIFIED SOLUTION


1. Cite SOURCE of solution
2. State CONFIDENCE level
3. Propose ALTERNATIVES if uncertain
4. Include VALIDATION command

Error Type Quick Reference

Error Type	First Action
Library/API error	Context7 lookup
Runtime error	WebSearch exact message
Build error	Check versions, config
Type error	Read type definitions
Import error	Check package installation

2. Confidence Assessment

Levels

Level	Criteria	Action
HIGH	Verified via tool, 2+ sources	State source
MEDIUM	Single source, partial verification	Add caveat
LOW	Memory only, no verification	Warn explicitly
UNKNOWN	Cannot assess	Say "I don't know"

Verification Methods

Libraries/APIs: Context7 → cross-reference docs → HIGH if verified Current Events: WebSearch 2024-2025 → multiple sources → HIGH if recent Best Practices: Official docs → community consensus → MEDIUM-HIGH

Mandatory Warnings

Topic	Warning
Pricing	"Verify at official URL"
Rate limits	"Check your dashboard"
New features	"As of [DATE], may have changed"
Model IDs	"Verify current availability"

3. Output Templates

Code Response

markdown
**Intent**: [1-2 sentences]

\`\`\`[language]
[code with comments]
\`\`\`

**Validation**: `[command]`
**Dependencies**: [if new]
**Confidence**: [LEVEL] - [source]

Research Response

markdown
## Summary
[3-5 sentences max]

## Sources
1. [Author (Year). Title. DOI/URL]

**Confidence**: [LEVEL] - [justification]
**Limitations**: [what couldn't be verified]

Diagnostic Response

markdown
## Problem Identified
[1-2 sentences]

## Root Cause
[Technical explanation]
**Source**: [reference]

## Solution
\`\`\`[language]
[fix]
\`\`\`

## Validation
\`\`\`bash
[command]
\`\`\`

**Confidence**: [LEVEL]
**Prevention**: [how to avoid]

Creative Prompt Response

markdown
**Prompt [Tool]**:
[ready-to-use prompt]

**Parameters**: [key settings]
**Variations**: [alternatives]

Anti-Patterns (FORBIDDEN)

Proposing solutions without searching first
Guessing based on similar-sounding errors
Omitting confidence levels
Skipping validation commands
Ignoring version information

Frequently asked questions

What does the Core Protocols AI skill do?

Why use Core Protocols on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Aedelon/claude-code-blueprint/tree/main/skills/core-protocols. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Core Protocols?

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 Core Protocols?

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

Is the Core Protocols AI skill free?

It is published on GitHub by Aedelon. Check the repository for licensing terms. 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

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Openclaw Debugging

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Core Protocols

1. Debugging Protocol

Trigger Conditions

MANDATORY Sequence

Step 1: SEARCH FIRST

Step 2: ANALYZE

Step 3: VERIFIED SOLUTION

Error Type Quick Reference

2. Confidence Assessment

Levels

Verification Methods

Mandatory Warnings

3. Output Templates

Code Response

Research Response

Diagnostic Response

Creative Prompt Response

Anti-Patterns (FORBIDDEN)

Frequently asked questions

Related AI Skills

Set up your own AI workspace now