kcp-render

Render external knowledge.yaml files to neutralize prompt injection and verify signatures.

25|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Cantara/knowledge-context-protocol --skill kcp-render
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcp-render
Source: https://github.com/Cantara/knowledge-context-protocol/tree/main/skills/kcp-render
Command: npx skills add https://github.com/Cantara/knowledge-context-protocol --skill kcp-render

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the security risk of directly exposing AI agents to potentially untrusted or malicious knowledge.yaml files by providing a safe, pre-rendering step using the KCP standard's render pipeline.

Core Features & Use Cases

  • Secure Ingestion: Renders external knowledge.yaml files to neutralize prompt injection and verify author signatures before content is exposed to the agent.
  • Dependency Verification: Processes manifests from external or federated sources, ensuring trust tiers (trusted, known, unsigned, failed) are respected.
  • Use Case: Safely integrate knowledge from a third-party GitHub repository by first running kcp render on their knowledge.yaml to validate its signature and trust level before allowing the agent to access its units.

Quick Start

Use kcp render path/to/external-knowledge.yaml --keys ~/.kcp/trusted-keys.yaml --out - to process an external manifest before passing the rendered output to the agent.

Frequently Asked Questions about kcp-render

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

FAQPage Schema
How do I safely render untrusted KCP manifests for AI agents?

To safely render untrusted KCP manifests, apply the deterministic KCP render pipeline to filter executable content and imperative instructions, preventing prompt injection before exposing knowledge.yaml files to AI agents.

What is the KCP render pipeline and how does it secure knowledge.yaml files?

The KCP render pipeline is a deterministic preprocessing step that secures knowledge.yaml files by neutralizing prompt injection, filtering executable content, and verifying author signatures before agent context enrichment.

How do I verify trust tiers and author signatures for external knowledge manifests?

Verify trust tiers and author signatures for external knowledge manifests by running the kcp render command with trusted keys, ensuring sources are categorized as trusted, known, unsigned, or failed before agent ingestion.

Can I integrate knowledge from a third-party GitHub repository into my AI agent safely?

Yes, you can safely integrate third-party GitHub repository knowledge by running kcp render on their external knowledge.yaml file to validate its signature and trust level before allowing the agent to access its units.

Does kcp render work without verifiable signatures on unsigned manifests?

Yes, kcp render processes unsigned manifests by assigning them an unsigned trust tier, allowing you to handle untrusted sources safely while filtering executable content and imperative instructions from the rendered output.

What are the limitations of preprocessing untrusted knowledge manifests for AI context enrichment?

The main limitation of preprocessing untrusted knowledge manifests is that while the render pipeline filters executable content and imperative instructions, it cannot inherently trust unsigned or failed sources without verifiable author signatures.