kcc-agentic-journaler

Route agentic learnings to Skill files or service-scoped journal paths.

1.1k|367|Updated Apr 8, 2019
One-click install
npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill kcc-agentic-journaler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kcc-agentic-journaler
Source: https://github.com/GoogleCloudPlatform/k8s-config-connector/tree/main/.gemini/skills/kcc-agentic-journaler
Command: npx skills add https://github.com/GoogleCloudPlatform/k8s-config-connector --skill kcc-agentic-journaler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents knowledge pollution and merge conflicts by ensuring agentic learnings are captured in the correct, contextually relevant location based on their scope.

Core Features & Use Cases

  • Hierarchical routing rules: Guides agents to decide whether a learning belongs in a general Skill update or in a service-scoped journal.
  • Service-scoped journal writes: Enforces writing to .gemini/journals/<service_name>.md for domain/service tribal knowledge to avoid cross-service merge conflicts.
  • Safe validation constraint: Explicitly prevents appending to centralized skill journals under .gemini/skills/.

Quick Start

Follow the Tier 1 or Tier 2 routing logic in the Skill instructions and write your learning to the specified file path for your task.

Frequently Asked Questions about kcc-agentic-journaler

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

FAQPage Schema
How do I prevent merge conflicts when recording agentic learnings across different services?

To prevent merge conflicts when recording agentic learnings, route service-specific domain knowledge to `.gemini/journals/<service_name>.md` and general mechanics to the relevant Skill's SKILL.md file.

What is the correct file path for service-scoped markdown updates in KCC?

The correct file path for service-scoped markdown updates in KCC is `.gemini/journals/<service_name>.md`, which isolates tribal knowledge to avoid cross-service merge conflicts.

How does agentic journaling route cross-cutting mechanics versus implementation quirks?

Agentic journaling routes cross-cutting mechanics by updating the relevant Skill's SKILL.md file, while appending service-specific implementation quirks to the designated service journal file.

Can I append agent knowledge to centralized journal.md files under .gemini/skills?

No, you cannot append agent knowledge to centralized journal.md files under `.gemini/skills/`. The routing rules explicitly forbid writing to this directory to prevent knowledge pollution.

When do I need to update a SKILL.md file instead of a service journal?

You need to update a SKILL.md file instead of a service journal when capturing general cross-cutting KCC mechanics, whereas domain knowledge or service-specific quirks belong in the service journal.

Why does my agent knowledge pollution affect multiple repository locations?

Agent knowledge pollution affects multiple repository locations when learnings are not correctly routed, which is why enforcing a two-tier hierarchy ensures general mechanics and domain knowledge are separated.