stdlib

Explain Kukicha stdlib authoring guidelines and governance for package creation and auditing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kukichalang/kukicha --skill stdlib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stdlib
Source: https://github.com/kukichalang/kukicha/tree/main/.claude/skills/stdlib
Command: npx skills add https://github.com/kukichalang/kukicha --skill stdlib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers and reviewers in authoring Kukicha stdlib packages, ensuring consistent structure, generation, testing, and security practices.

Core Features & Use Cases

  • Metadata-guided package structure: Each stdlib package lives under stdlib/<name>/ with a .kuki source and a generated .go, plus test files.
  • Security patterns and pitfalls coverage: Provides documented checks for SQL, XSS, SSRF, and other common risks, plus guidance to avoid unsafe patterns.
  • Governance and tooling: Describes registry generation, deprecation, and audit workflows (e.g., make genstdlibregistry, kukicha audit).
  • Testing and validation: Enforces *_test.kuki files and table-driven tests for reliability.

Quick Start

Write a stdlib .kuki, run make generate to produce the Go code, and validate the package against the registry and security rules.

Frequently Asked Questions about stdlib

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

FAQPage Schema
How do I author a Kukicha stdlib package with the correct structure?

Authoring a Kukicha stdlib package requires placing a .kuki source and generated .go file under stdlib/<name>/, ensuring the SKILL.md frontmatter includes the required name and description fields.

What is the workflow for generating and validating Kukicha stdlib packages?

The stdlib generation workflow involves writing a .kuki file, running make generate to produce Go code, and validating the resulting package against the registry using make genstdlibregistry.

How does Kukicha stdlib governance handle security risks like SQL injection and XSS?

Kukicha stdlib governance handles security risks by applying documented checks for SQL, XSS, and SSRF during package auditing, flagging potential vulnerabilities and enforcing safe code generation patterns.

Do I need table-driven tests for Kukicha stdlib package validation?

Yes, Kukicha stdlib validation requires table-driven tests. You must include *_test.kuki files alongside your package source to enforce reliability and pass standard governance audits.

How do I audit a Kukicha stdlib package for compute dependencies and security vulnerabilities?

You audit a Kukicha stdlib package by running the kukicha audit command to compute dependencies and components from scripts, references, and assets, which actively flags potential security risks.

When should I deprecate a Kukicha stdlib package?

You should deprecate a Kukicha stdlib package when it no longer meets governance practices or security rules, utilizing the documented registry generation and deprecation workflows to safely retire it.