cks-usage

Name: cks-usage
Availability: InStock
Author: enduser123

Enforce CKS knowledge ingestion through the DirectCKSIngestion API instead of flat-file writes.

Updated Apr 23, 2026

Search Tags:#security #verification #ingestion #knowledge-management #api-first #data-governance #cks

Ready to run

npx skills add https://github.com/EndUser123/cc-skills-utils --skill cks-usage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cks-usage
Source: https://github.com/EndUser123/cc-skills-utils/tree/main/skills/cks-usage
Command: npx skills add https://github.com/EndUser123/cc-skills-utils --skill cks-usage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures all knowledge is ingested into the CKS database via the DirectCKSIngestion API, preventing flat-file storage and ad-hoc file I/O that bypasses the knowledge-management workflow.

Core Features & Use Cases

Detects violations such as JSON writes to data/cks, file-based knowledge storage outside the CKS, or triggering /learn manually.
Guides users through the proper ingestion workflow using DirectCKSIngestion.ingest_knowledge, followed by verification with search_knowledge and statistics via get_statistics.
Provides a governance loop to audit ingestion attempts and enforce API-first knowledge management.

Quick Start

Ingest knowledge using the DirectCKSIngestion API to replace any flat-file storage or JSON writes.

Frequently Asked Questions about cks-usage

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

FAQPage Schema

How do I prevent flat-file knowledge storage from bypassing the CKS ingestion API?▼

Knowledge ingestion via the CKS API prevents flat-file storage by requiring all data to flow through the DirectCKSIngestion.ingest_knowledge workflow. This replaces ad-hoc JSON writes to data/cks and manual /learn invocations with governed API-first ingestion.

What is the proper workflow for CKS knowledge ingestion and verification?▼

The proper workflow for CKS knowledge ingestion involves calling DirectCKSIngestion.ingest_knowledge to load data, verifying the ingestion with search_knowledge, and reporting statistics with get_statistics to ensure data governance compliance.

Why does writing JSON directly to data/cks cause knowledge management issues?▼

Writing JSON directly to data/cks causes knowledge management issues because it bypasses the DirectCKSIngestion API, leading to ungoverned flat-file storage. This prevents proper indexing, searchability, and statistical tracking within the CKS database.

Can I use the /learn command instead of the DirectCKSIngestion API for knowledge ingestion?▼

No, you cannot use the /learn command for knowledge ingestion. Triggering /learn manually is treated as a violation of the API-first workflow; you must use the DirectCKSIngestion.ingest_knowledge flow to properly ingest data into the CKS database.

How do I verify knowledge ingestion and report statistics after using the CKS API?▼

To verify knowledge ingestion and report statistics after using the CKS API, use search_knowledge to confirm the data is accessible, then call get_statistics to report post-ingestion metrics and complete the governance audit loop.