Agent skill

Claude Code Knowledge

by dykyi-roman in dykyi-roman/awesome-claude-code

Comprehensive knowledge base for Claude Code formats, patterns, and configuration.

MITAuto-check passedAgent Workflows

Install Claude Code Knowledge

skills CLI
$ npx skills add dykyi-roman/awesome-claude-code --skill claude-code-knowledge -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dykyi-roman/awesome-claude-code claude-code-knowledge --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dykyi-roman/awesome-claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/claude-code-knowledge .claude/skills/claude-code-knowledge && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
claude-code-knowledge
GitHub stars
103
Token cost
~4k tokens
SKILL.md length
1,079 words
Files
7 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Comprehensive knowledge base for Claude Code formats, patterns, and configuration.

  • Auditing commands
  • SKILL.md covers Component Types Overview, Commands, Agents (Subagents) and Skills, plus 9 more sections
  • Calls claude; reaches github.com; needs API_KEY
  • Tasks that involve Knowledge bases

What it does

Claude Code Knowledge is an agent skill from dykyi-roman/awesome-claude-code. Comprehensive knowledge base for Claude Code formats, patterns, and configuration. Use when creating, improving, or auditing commands, agents, skills, hooks, memory, plugins, or settings.

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/hooks-reference.md`, `references/memory-and-rules.md` and `references/plugins-reference.md`).

It sits in Agent Workflows, covering Knowledge bases and Agent instruction files. The repository describes itself as: PHP Architecture Toolkit for Claude Code (DDD, CQRS, Event Sourcing, Hexagonal, Clean Architecture, SOLID, GRASP, PSR, Design Patterns, Testing, Documentation, Code Review). The licence is MIT.

When your agent uses it

  • Auditing commands
  • Tasks that involve Knowledge bases
  • Tasks that involve Agent instruction files

Example prompts

  • “/claude-code-knowledge”

Requirements

  • A credential in API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 7e1fea8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Claude Code Knowledge loads about 4k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 1,079 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~15k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dykyi-roman/awesome-claude-code at commit 7e1fea8, republished under its MIT licence (© dykyi-roman). 1,079 words, ~4,023 tokens.

Download SKILL.mdSave it as .claude/skills/claude-code-knowledge/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
claude-code-knowledge
description
Comprehensive knowledge base for Claude Code formats, patterns, and configuration. Use when creating, improving, or auditing commands, agents, skills, hooks, memory, plugins, or settings.

Claude Code Knowledge Base

Component Types Overview

TypePathInvocationContext Cost
Command.claude/commands/name.md/name argsLoaded on invocation
Agent.claude/agents/name.mdTask(subagent_type)Loaded into subagent context
Skill.claude/skills/name/SKILL.mdAuto or /nameLoaded by description match
Hook.claude/settings.jsonAutomatic on eventZero (shell script)
Rules.claude/rules/*.mdAuto-loaded alwaysAlways in system prompt
MemoryCLAUDE.md (various levels)Auto-loaded alwaysAlways in system prompt

Commands

Path: .claude/commands/name.md Invocation: /name or /name arguments

yaml
---
description: Required. What the command does.
allowed-tools: Optional. Restrict tools (comma-separated).
model: Optional. opus/sonnet/haiku — or alias from settings.
argument-hint: Optional. Hint shown in autocomplete.
---

Command instructions here.

Use $ARGUMENTS for full argument string.
Use $ARGUMENTS[0], $ARGUMENTS[1] for positional args.
Use $1, $2 as shorthand for $ARGUMENTS[N].
Use ${CLAUDE_SESSION_ID} for session identifier.

Key rules:

  • Equivalent to .claude/skills/name/SKILL.md with user-invocable: true
  • Commands in subdirectories: .claude/commands/sub/name.md → /sub/name
  • Budget: SLASH_COMMAND_TOOL_CHAR_BUDGET (default 15000 chars)

Agents (Subagents)

Path: .claude/agents/name.md Invocation: Task tool with subagent_type="name"

yaml
---
name: agent-name            # required, matches filename without .md
description: Required. When to use. "PROACTIVELY" for auto-invoke.
tools: Optional. All by default. Comma-separated.
disallowedTools: Optional. Denylist complement to tools.
model: Optional. opus | sonnet | haiku | inherit
permissionMode: Optional. default | plan | acceptEdits | auto | dontAsk | bypassPermissions | delegate
skills: Optional. Auto-load skills (comma-separated inline list).
hooks: Optional. Lifecycle hooks scoped to this agent.
memory: Optional. user | project | local — CLAUDE.md scope to load.
---

Agent system prompt here.

Permission modes:

  • default — ask user for each tool use
  • acceptEdits — auto-allow file edits, ask for others
  • plan — read-only exploration, no writes
  • dontAsk — run without asking, within sandbox
  • delegate — inherit parent permissions
  • bypassPermissions — skip all permission checks (dangerous)

Built-in subagent types: Explore, Plan, general-purpose, Bash, statusline-setup, claude-code-guide

Execution: foreground (blocks) or background (run_in_background: true). Resume via agent ID.

Scope priority: CLI --agents flag > project .claude/agents/ > user ~/.claude/agents/ > plugin agents


Skills

Path: .claude/skills/name/SKILL.md Invocation: /name (if user-invocable) or auto-loaded by agent/description match

yaml
---
name: skill-name            # lowercase, hyphens, max 64 chars
description: Required. What and when. Max 1024 chars.
allowed-tools: Optional. Restrict tools.
model: Optional. Model override when skill is active.
context: Optional. "fork" for isolated subagent execution.
agent: Optional. Which subagent type to run in (Explore, Plan, etc).
hooks: Optional. Lifecycle hooks scoped to this skill.
disable-model-invocation: true   # only user can invoke
user-invocable: false            # only Claude can invoke
---

Skill instructions here.

Use $ARGUMENTS, $ARGUMENTS[N], $N for user input.
Use !`command` for dynamic context injection (shell output inserted).

Folder structure:

skill-name/
├── SKILL.md        # required, max 500 lines
├── references/     # large content extracted here
├── scripts/        # executable code
└── assets/         # templates, resources

Invocation control matrix:

disable-model-invocationuser-invocableWho can invoke
false (default)true (default)Both user and Claude
truetrueUser only (via /name)
falsefalseClaude only (auto-load)
truefalseNobody (disabled)

Hooks

Path: .claude/settings.json (or agent/skill frontmatter hooks: field)

Hook Events

Verified against Claude Code 2.1.233 with claude plugin validate — an unknown event name is rejected as hooks.<Name>: Invalid key in record, so this list is checked, not remembered.

GroupEvents (matcher support noted where applicable)
Tool executionPreToolUse, PostToolUse, PostToolUseFailure, PostToolBatch, PermissionRequest, PermissionDenied — all take a tool-name matcher
Turn lifecycleUserPromptSubmit, UserPromptExpansion, Stop, StopFailure
Agents & tasksSubagentStart, SubagentStop, TeammateIdle, TaskCreated, TaskCompleted
SessionSessionStart, SessionEnd, Setup
ContextPreCompact, PostCompact, Notification, MessageDisplay
EnvironmentFileChanged, CwdChanged, DirectoryAdded, ConfigChange, InstructionsLoaded, WorktreeCreate, WorktreeRemove
MCPElicitation, ElicitationResult

Blocking is done with exit code 2 (exit 1 is a non-blocking error). PreToolUse may also return JSON with permissionDecision: "deny". See references/hooks-reference.md for per-event payloads and blocking semantics.

Never generate these — they do not exist. A hook registered under an invented name silently never fires, and claude plugin validate rejects the plugin with Invalid key in record:

Invented nameUse instead
ToolErrorPostToolUseFailure
PreUserInputUserPromptSubmit
PostUserInputStop
Hook Types (3)
json
{"type": "command", "command": "./script.sh"}
{"type": "prompt", "prompt": "Check if output is safe"}
{"type": "agent", "agent": "validator-agent"}
Exit Codes
CodeBehavior
0Allow (continue)
2Block (deny tool use, PreToolUse only)
OtherLog warning, continue
Hook Configuration
json
{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {"type": "command", "command": "php -l $CLAUDE_FILE_PATH", "async": false}
        ]
      }
    ]
  }
}

Matcher patterns: exact name, | OR, regex. MCP tools: mcp__server__tool.

For comprehensive hooks reference see references/hooks-reference.md.


Memory & CLAUDE.md

Hierarchy (top to bottom, higher = higher priority)
LevelLocationScope
ManagedSystem dirs (enterprise)Organization-wide
User~/.claude/CLAUDE.mdAll user projects
User rules~/.claude/rules/*.mdAll user projects
ProjectCLAUDE.md (project root)This project
Project rules.claude/rules/*.mdThis project
LocalCLAUDE.local.md (project root, auto-gitignored)This machine only
Nestedsrc/CLAUDE.md, tests/CLAUDE.mdSubdirectory context
Rules Files

.claude/rules/*.md — modular rules, always loaded into system prompt.

Path-specific rules via paths frontmatter:

yaml
---
paths:
  - src/Domain/**
  - src/Application/**
---
These rules apply only when working with files matching the glob patterns above.
Import Syntax
markdown
@path/to/file.md      # relative to current file
@/absolute/path.md    # absolute path
@~/user/path.md       # home directory

Import recursion limit: 5 hops max.

Commands
  • /memory — view and edit memory files
  • /init — generate initial CLAUDE.md from project analysis

For full reference see references/memory-and-rules.md.


Plugins

Path: .claude-plugin/plugin.json (plugin root)

json
{
  "name": "my-plugin",
  "description": "What this plugin provides",
  "version": "1.0.0",
  "author": "Name",
  "repository": "https://github.com/user/repo"
}

Plugin structure. Only the manifests live inside .claude-plugin/; every component directory sits at the plugin root, next to it — not inside it:

my-plugin/                  # plugin root
├── .claude-plugin/
│   ├── plugin.json         # manifest (required)
│   └── marketplace.json    # only when this repo is also a marketplace
├── commands/               # namespaced as /plugin:command
├── agents/                 # available as subagent_type "plugin:agent"
├── skills/<name>/SKILL.md  # namespaced as /plugin:skill
├── hooks/hooks.json        # plugin-scoped hooks
├── .mcp.json               # MCP servers (or an "mcpServers" key in plugin.json)
└── .lsp.json               # LSP server config

Putting commands/ or skills/ inside .claude-plugin/ makes them invisible — the loader looks for them at the plugin root.

Namespaced invocation: /plugin-name:skill-name

Installation sources: GitHub, Git URL, NPM, File path, Directory.

For full reference see references/plugins-reference.md.


Permissions

Rule Syntax
json
{
  "permissions": {
    "allow": ["Read", "Glob", "Grep"],
    "deny": ["Bash(rm *)"],
    "ask": ["Write", "Edit"]
  }
}

Specifier patterns:

PatternExampleMatches
ToolReadAll Read calls
Tool(literal)Bash(npm test)Exact command
Tool(glob)Read(src/**)Gitignore-style glob
Tool(domain:)WebFetch(domain:api.example.com)Domain filter
mcp__server__toolmcp__github__create_issueMCP tool
Task(agent)Task(ddd-auditor)Specific subagent

Evaluation order: deny → ask → allow (deny wins over allow)

For full reference see references/settings-and-permissions.md.


MCP (Model Context Protocol)

Config: .mcp.json (project root) or in settings.json

json
{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-name"],
      "env": {"API_KEY": "..."}
    }
  }
}

Tool naming: mcp__servername__toolname

Scope hierarchy: project .mcp.json > user settings > plugin .mcp.json

Permission: enableAllProjectMcpServers, allowedMcpServers, deniedMcpServers in settings.


Show full SKILL.md (441 more words)Show less

Settings

Hierarchy: managed > CLI args > local > project > user

LevelLocation
User~/.claude/settings.json
Project.claude/settings.json
Local.claude/settings.local.json (gitignored)
ManagedEnterprise system dirs

Key settings areas: permissions, hooks, sandbox, MCP, model config, context management, attribution.

For full schema reference see references/settings-and-permissions.md.


Decision Framework

When to use which component type:

GoalBest ComponentReason
Reusable saved promptCommandUser invokes, low context cost
Complex analysis in isolationAgentSeparate context window
Knowledge base / templatesSkillAuto-loaded, shared across agents
Auto-trigger on eventsHookZero context cost, shell execution
Project-wide instructionsCLAUDE.mdAlways in context
Path-specific rulesRules (.claude/rules/)Conditional loading
Distributable extensionPluginNamespaced, installable
External tool integrationMCPStandardized protocol
Context Cost Awareness
ComponentContext Budget Impact
CLAUDE.md + rulesAlways loaded (~500 lines recommended max)
Skills (auto-loaded)Loaded when description matches (~15K chars budget)
Skills (by agent)Loaded into agent's context window
AgentsSeparate context window (no parent cost)
Hooks (command type)Zero context cost (shell execution)
Hooks (prompt/agent type)Uses context for LLM evaluation
MCP toolsTool descriptions always in context
PluginsComponents loaded per their type rules

Patterns

Parallel Agents
Run in parallel:
1. Task: researcher — study architecture
2. Task: security-scanner — check security
3. Task: performance-analyzer — check performance

Wait for all and combine results.
Progressive Disclosure
SKILL.md — brief instructions (max 500 lines)
references/ — details loaded when needed
scripts/ — execute without reading into context
Chained Agents
1. researcher → studies the task
2. planner → creates plan based on research
3. implementer → implements the plan
4. reviewer → reviews implementation
Agent Teams (Coordinator Pattern)
coordinator (opus) → delegates via Task tool
├── auditor-1 (sonnet, parallel)
├── auditor-2 (sonnet, parallel)
└── generator (sonnet, sequential after audit)

Coordinator uses TaskCreate/TaskUpdate for progress tracking.
Plugin Distribution
Package as .claude-plugin/ → publish to GitHub/NPM
Users install: enabledPlugins in settings
Skills namespaced: /plugin-name:skill-name

Validation Checklists

Commands
  • description is filled and specific
  • Path: .claude/commands/*.md
  • $ARGUMENTS used if argument-hint defined
  • model specified consciously (opus for complex, haiku for fast)
  • Instructions are clear and step-by-step
Agents
  • name and description are filled
  • name matches filename (without .md)
  • tools are minimally necessary
  • disallowedTools used if most tools needed except few
  • model chosen consciously
  • permissionMode appropriate for task
  • skills: is comma-separated inline list (not YAML array)
  • Coordinators have TaskCreate, TaskUpdate in tools
  • Coordinators have task-progress-knowledge in skills
Skills
  • name is lowercase with hyphens, matches folder name
  • description < 1024 characters, explains "when to use"
  • SKILL.md < 500 lines
  • Large content extracted to references/
  • context: fork if needs isolated execution
  • Path: .claude/skills/name/SKILL.md
Hooks
  • JSON is valid
  • Event name is one of 12 valid events
  • matcher is correct tool/agent name or pattern
  • command script exists and is executable
  • Exit codes handled properly (0=allow, 2=block)
  • async: true only for non-blocking operations
Memory/Rules
  • CLAUDE.md < 500 lines (recommended)
  • .claude/rules/*.md for modular rules
  • CLAUDE.local.md in .gitignore
  • @imports resolve (max 5 hops)
  • paths frontmatter uses valid glob patterns
Settings
  • Valid JSON in settings.json
  • Permission rules follow deny → ask → allow order
  • settings.local.json is gitignored
  • Sandbox configured if auto-allowing Bash
  • MCP servers explicitly allowed/denied

Reference Files

Detailed documentation for specific areas:

© dykyi-roman, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/claude-code-knowledge of dykyi-roman/awesome-claude-code.

  • SKILL.md
  • references/hooks-reference.md
  • references/memory-and-rules.md
  • references/plugins-reference.md
  • references/settings-and-permissions.md
  • references/skills-advanced.md
  • references/subagents-advanced.md

Open the folder on GitHubat commit 7e1fea8

Compare with similar skills

Claude Code Knowledge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Claude Code Knowledge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Claude Code Knowledge this skilldykyi-roman/awesome-claude-code103—~4kAutomated safety check: PassMIT
Docs Gardeningmhmzdev/the-holy-quran-app889—~1.1kAutomated safety check: PassMIT
Sake Workflowkattouf/Sake116—~935Automated safety check: PassMIT
Project InitBlackBeltTechnology/pi-agent-dashboard315—~3.4kAutomated safety check: PassMIT
Project Memoryjamditis/claude-skills-journalism416—~2.5kAutomated safety check: NotesMIT
Memory Managementw95/awesome-claude-corporate-skills2371 repos~2.2kAutomated safety check: PassMIT

Similar skills

  • Docs Gardening

    mhmzdev/the-holy-quran-app

    Audit and maintain The Holy Qur'an app's knowledge base (AGENTS.md, .agents/rules/, docs/ OKF bundle) for staleness, broken cross-links, drift from code, and OKF structural issues.

    889 GitHub stars~1.1k tokensUpdated 28 days ago
    Agent WorkflowsAuto-check passed
  • Sake Workflow

    kattouf/Sake

    A skill your agent uses when starting any new task in the Sake project - ensures structured execution with knowledge discovery, quality checks, and organic growth of the project knowledge base…

    116 GitHub stars~935 tokensUpdated 6 mo ago
    Agent WorkflowsAuto-check passed
  • Project Init

    BlackBeltTechnology/pi-agent-dashboard

    Scaffold an unconfigured directory into a configured pi project.

    315 GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Project Memory

    jamditis/claude-skills-journalism

    Generates CLAUDE.md project memory files that transfer institutional knowledge.

    416 GitHub stars~2.5k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check: notes
  • Memory Management

    w95/awesome-claude-corporate-skills

    Two-tier memory system that makes Claude a true workplace collaborator.

    237 GitHub starsUsed in 1 repo~2.2k tokens
    Agent WorkflowsAuto-check passed
  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from dykyi-roman/awesome-claude-code

All 11 skills in this repo
  • Grasp Knowledge

    dykyi-roman/awesome-claude-code

    GRASP principles knowledge base for PHP 8.4 projects. An agent skill from dykyi-roman/awesome-claude-code.

    103 GitHub stars~1.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Psr Autoloading Knowledge

    dykyi-roman/awesome-claude-code

    PSR-4 autoloading standard knowledge base for PHP 8.4 projects.

    103 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Psr Coding Style Knowledge

    dykyi-roman/awesome-claude-code

    PSR-1 and PSR-12 coding standards knowledge base for PHP 8.4 projects.

    103 GitHub stars~2.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Psr Overview Knowledge

    dykyi-roman/awesome-claude-code

    PHP Standards Recommendations (PSR) overview knowledge base.

    103 GitHub stars~2.7k tokensUpdated 1 mo ago
    Auto-check passed
  • Solid Knowledge

    dykyi-roman/awesome-claude-code

    SOLID principles knowledge base for PHP 8.4 projects. An agent skill from dykyi-roman/awesome-claude-code.

    103 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Adr Knowledge

    dykyi-roman/awesome-claude-code

    Action-Domain-Responder pattern knowledge base. An agent skill from dykyi-roman/awesome-claude-code.

    103 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Claude Code Knowledge

What does Claude Code Knowledge do?

Comprehensive knowledge base for Claude Code formats, patterns, and configuration. Claude Code Knowledge is an agent skill from dykyi-roman/awesome-claude-code. Comprehensive knowledge base for Claude Code formats, patterns, and configuration.

When should I use Claude Code Knowledge?

Claude Code Knowledge fits situations like: auditing commands; tasks that involve Knowledge bases; tasks that involve Agent instruction files.

How do I install Claude Code Knowledge in Claude Code?

Run `npx skills add dykyi-roman/awesome-claude-code --skill claude-code-knowledge -a claude-code`. Or copy the skill folder (skills/claude-code-knowledge in dykyi-roman/awesome-claude-code) into .claude/skills/claude-code-knowledge in your project. Claude Code loads it when a task matches its description.

How do I install Claude Code Knowledge in Codex?

Run `npx skills add dykyi-roman/awesome-claude-code --skill claude-code-knowledge -a codex`. Or copy the skill folder (skills/claude-code-knowledge in dykyi-roman/awesome-claude-code) into .agents/skills/claude-code-knowledge in your project. Codex loads it when a task matches its description.

Can I use Claude Code Knowledge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dykyi-roman/awesome-claude-code --skill claude-code-knowledge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claude-code-knowledge, .gemini/skills/claude-code-knowledge, .github/skills/claude-code-knowledge and .opencode/skills/claude-code-knowledge in your project.

What does Claude Code Knowledge need to run?

Going by SKILL.md and its folder, Claude Code Knowledge needs the command-line tools its instructions call (claude) and credentials named API_KEY. Our summary lists: A credential in API_KEY.

Does Claude Code Knowledge access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Claude Code Knowledge safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Claude Code Knowledge use?

Claude Code Knowledge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Claude Code Knowledge use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Claude Code Knowledge?

Skills that share tags, products or a category with Claude Code Knowledge: Docs Gardening (mhmzdev/the-holy-quran-app, 889 stars), Sake Workflow (kattouf/Sake, 116 stars), Project Init (BlackBeltTechnology/pi-agent-dashboard, 315 stars) and Project Memory (jamditis/claude-skills-journalism, 416 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Claude Code Knowledge?

dykyi-roman (a GitHub user) maintains it in dykyi-roman/awesome-claude-code, which has 103 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 16, 2026.

Source: dykyi-roman/awesome-claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.