ravnhq/platform-cli
skills/cli/platform-cli/SKILL.md
Design and implementation patterns for building command-line tools with modern UX. Use when designing a CLI, reviewing CLI UX, defining commands and flags, or implementing error handling and signal handling.
$ install --global
skillsauthnpx skillsauth add ravnhq/ai-toolkit platform-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 9:46 AM54.3s11 files scanned
SKILL.md
- name:
- platform-cli
- description:
- Design and implementation patterns for building command-line tools with
- category:
- cli
- extends:
- core-coding-standards
- status:
- ready
- version:
- 5
CLI Development Patterns
Modern CLI design patterns for commands, flags, output, errors, signals, config, and distribution.
Rules
Core CLI design rules extracted as discrete, actionable patterns. See rules index for the full list organized by:
- Commands & Naming - Lowercase, typeable command names
- Flags & Arguments - Standard flag conventions (-h, -v, -q, etc.)
- Configuration - Precedence order (flags > env > config > defaults)
- Output & Streams - stdout vs stderr separation
- Error Handling - Actionable error messages with clear fixes
- Signals & Lifecycle - Ctrl-C handling with timeout and force option
- Security - Never read secrets from environment variables
- Distribution - Single binary packaging when possible
References
See references/cli-patterns.md for comprehensive guidance organized by:
- Design & Naming - Command structure, naming conventions, future-proofing
- Flags & Arguments - Standard flags, short forms, boolean negation
- Output & Formatting - stdout/stderr, TTY detection, colors, machine-readable formats
- Error Handling - Exit codes, error messages, signal-to-noise ratio
- Signals & Lifecycle - Ctrl-C handling, cleanup timeouts
- Environment & Config - Standard variables, precedence, naming
- Distribution & Packaging - Single binary distribution, uninstall instructions
- Security & Privacy - Secret handling, telemetry consent
Examples
Positive Trigger
User: "Design CLI commands, flags, and exit codes for a deployment tool."
Expected behavior: Use platform-cli guidance, follow its workflow, and return actionable output.
Non-Trigger
User: "Write a migration plan for PostgreSQL partitioning."
Expected behavior: Do not prioritize platform-cli; choose a more relevant skill or proceed without it.
Troubleshooting
Skill Does Not Trigger
- Error: The skill is not selected when expected.
- Cause: Request wording does not clearly match the description trigger conditions.
- Solution: Rephrase with explicit domain/task keywords from the description and retry.
Guidance Conflicts With Another Skill
- Error: Instructions from multiple skills conflict in one task.
- Cause: Overlapping scope across loaded skills.
- Solution: State which skill is authoritative for the current step and apply that workflow first.
Output Is Too Generic
- Error: Result lacks concrete, actionable detail.
- Cause: Task input omitted context, constraints, or target format.
- Solution: Add specific constraints (environment, scope, format, success criteria) and rerun.
Workflow
- Identify whether the request clearly matches
platform-cliscope and triggers. - Apply the skill rules and referenced guidance to produce a concrete result.
- Validate output quality against constraints; if gaps remain, refine once with explicit assumptions.
Related Skills
ravnhq/promptify
testing
VerifiedTrustedCommunity
Transform user requests into detailed, precise prompts for AI models. Use when users say 'promptify', 'promptify this', 'rewrite this prompt', 'make this prompt better/more specific', or explicitly request prompt engineering or improvement of their request for better AI responses.
15SKILL.mdUpdated Apr 23, 2026
ravnhq/agent-skills-manager
tools
VerifiedTrustedCommunity
Manage AI skills from the Ravn AI Toolkit via corvus CLI — install, update, remove, search, and configure skills for any project. Use when: (1) Installing AI skills into a project, (2) Updating installed skills to latest versions, (3) Browsing or searching available skills, (4) Configuring global or per-project skill sets, (5) Troubleshooting corvus setup. Triggers on: "install skills", "add skills", "update skills", "corvus", "skill manager", "browse skills", "set up AI rules".
15SKILL.mdUpdated Apr 19, 2026
ravnhq/design-variations
development
VerifiedTrustedCommunity
Generate a gallery of design variations for a UI component. Takes an existing component (referenced by name, pasted code, or screenshot) and produces N distinct rendered alternatives in a single comparison page. Use when exploring visual directions, generating mockups, comparing design approaches for a component, creating A/B candidates, or when anyone says "show me options" or "give me variations" for a UI element.
14SKILL.mdUpdated Apr 23, 2026
ravnhq/qa-personality-builder
tools
VerifiedTrustedCommunity
Create custom QA agent personalities for project-specific testing needs. Guided builder that asks about the specialty, tools, and test scenarios, then generates a personality file and registers it in the QA config. Trigger on "create a QA personality", "add a custom test agent", "build a webhook tester", or when the user needs a project-specific QA agent. Also triggered by /qa-create-personality.
13SKILL.mdUpdated Apr 28, 2026