skills.rest
LiorCohen
LiorCohenCOMMUNITY
Explore all skills by this author →
GitHub

system-cli-standards

Enforce deterministic SDD system CLI invocation patterns for plugin prompts.

39|3|Updated Nov 21, 2025
Search Tags:#security#cli#audit#guidelines#prompt-standardization#system-run.sh#plugin-prompt
One-click install
npx skills add https://github.com/LiorCohen/sdd --skill system-cli-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-cli-standards
Source: https://github.com/LiorCohen/sdd/tree/main/.claude/skills/system-cli-standards
Command: npx skills add https://github.com/LiorCohen/sdd --skill system-cli-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standards for how plugin prompt files (skills, agents, commands) invoke and reference the SDD system CLI. Does NOT cover hooks (separate lifecycle via hook-runner.sh).

Core Features & Use Cases

  • Canonical Invocation guidelines for system-run.sh usage and consistent CLI access
  • Invocation Contexts, Output Contract, Stdin convention, and Authority Boundaries to ensure safe prompts
  • Audit procedures to ensure prompts remain compliant with CLI standards

Quick Start

Follow these standards to structure prompts so they invoke the SDD system CLI deterministically.

Frequently Asked Questions about system-cli-standards

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

FAQPage Schema
How do I enforce safe CLI invocation patterns for plugin prompts?▼

To enforce safe CLI invocation patterns, apply standardized frontmatter validation, canonical system-run.sh usage, and strict input/output handling to ensure deterministic execution for plugin prompts.

What is the canonical way to invoke system-run.sh in a plugin workflow?▼

The canonical way to invoke system-run.sh involves following established guidelines for invocation contexts, stdin conventions, and output contracts to coordinate file operations and formatting safely.

How do I audit prompts for CLI compliance and security?▼

Audit prompts for CLI compliance by running specified audit procedures that verify frontmatter validation, authority boundaries, and deterministic system-run.sh usage within the plugin workflow.

Does this CLI standardization apply to hooks and hook-runner.sh?▼

No, this CLI standardization does not apply to hooks. Hooks operate via a separate lifecycle managed by hook-runner.sh, while these standards specifically target skills, agents, and commands.

What authority boundaries should I set for CLI prompt safety?▼

Authority boundaries for CLI prompt safety restrict what a prompt can invoke, ensuring deterministic system-run.sh access, controlled file operations, and validated output formatting within the plugin workflow.

Related Skills

Explore More Software Engineering Skills→
BennettPhilBennettPhil

agent-friendly-builder

Generate Agent Skills with structured SKILL.md frontmatter and deterministic execution steps.

Community
Intermediate
anthrilanthril
3

cli-ux-audit

Audit CLI help, commands, errors, and accessibility with reproducible scored reports.

Official
Advanced
andreadellacorteandreadellacorte
5

groove-admin-cursor-hooks

Install and configure Cursor IDE hooks for the Groove workflow system.

Community
Intermediate
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate