add-embedded-prompt-knowledge

Embeds concise capability pointers into the compiled core's always-injected system prompt.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill add-embedded-prompt-knowledge-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-embedded-prompt-knowledge
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/add-embedded-prompt-knowledge
Command: npx skills add https://github.com/catalystctl/catcode --skill add-embedded-prompt-knowledge-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a capability must be recognized by the compiled Catalyst Code binary in any workspace—including a fresh install with no source tree or skills on disk—opt-in skills are not enough because they are not shipped by the installers. This Skill guides you through embedding a lean pointer into the always-injected system prompt so the agent recognizes the task everywhere. ## Core Features & Use Cases - Embedded const authoring: Add a raw-string const in core/src/main.rs near SYSTEM_PROMPT_BASE, PLUGIN_DOCS, and PROVIDER_GUIDE containing task recognition, a decision rule, and minimal actionable detail. - Correct injection placement: Inject unconditionally before the if with_skill block for main agent and subagents, or inside it for main-only visibility. - Size-guard maintenance: Update the standing_prompt_stays_lean_and_defers_plugin_manual test by adding the new const's length to the fixed sum and raising the ceiling modestly when needed. - Use Case: A user asks to ensure the core knows how to add providers via config or plugins; you add a ~1245-char PROVIDER_GUIDE const, inject it after PLUGIN_DOCS, and raise the test ceiling from 3500 to 4500. ## Quick Start Ask the agent to make the compiled core aware of a capability by embedding a lean pointer in the system prompt and updating the lean-prompt guard test.

Frequently Asked Questions about add-embedded-prompt-knowledge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make the compiled core aware of a new capability?

Add a lean raw-string const in core/src/main.rs near SYSTEM_PROMPT_BASE containing task recognition, a decision rule, and minimal actionable detail, then inject it in build_system_prompt(). Keep it a pointer that defers the full manual to a skill.

Why are opt-in skills not enough for standing agent knowledge?

Skills in .catalyst-code/skills/ are loaded from disk only on explicit invocation and are not copied by install.sh or install.ps1. A fresh install has no skills on disk, so only embedded consts spliced into the system prompt survive compilation.

Where should the new const be injected in build_system_prompt()?

Inject before the if with_skill block unconditionally when both the main agent and subagents should see it, matching PLUGIN_DOCS and PROVIDER_GUIDE. Inject inside if with_skill for main-agent-only knowledge, matching SUBAGENT_ORCHESTRATOR_STUB.

How do I update the standing prompt size-guard test?

Add your new const's length to the fixed sum in standing_prompt_stays_lean_and_defers_plugin_manual. If the total exceeds the ceiling, raise it modestly with roughly 8-15% headroom, then verify with cargo test --bins and cargo check --bins.

When should I embed a prompt pointer instead of writing code?

Embed a pointer when the agent must recognize a task and know the relevant paths, such as adding a provider via config or plugin. If the user wants new behavior rather than recognition, that is a code change handled by add-core-tool or add-config-knob instead.