cli

Discover and execute SkillFlaw skills and workflows via skillflaw-cli tree navigation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents users from guessing SkillFlaw node identifiers or bypassing official CLI flows when handling real enterprise business tasks like HR, reimbursements, procurement, approvals, contracts, and customer service.

Core Features & Use Cases

  • Skill discovery before action: Locate the correct tenant/business/project context and the target skill/workflow via the SkillFlaw CLI tree.
  • Controlled skill/workflow operations: Read generated skill markdown, save or download skill assets/bundles, and run workflows using the discovered node/flow context.
  • Guardrails for correctness: Enforces required preconditions (auth/baseUrl/key/payload validity) and blocks direct HTTP calls or identifier guessing.

Quick Start

Ask the assistant to run skillflaw-cli to find the correct project and skill node via the tree, then read the generated SKILL.md for that node.

Frequently Asked Questions about cli

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

FAQPage Schema
How do I discover and execute enterprise business workflows without guessing node identifiers?

To discover and execute enterprise workflows safely, you must use the skillflaw-cli to navigate the tree structure for node localization. This enforces guardrails by validating JSON payloads and prevents guessing identifiers or bypassing official CLI flows for HR, procurement, and approval tasks.

Can I use direct HTTP requests to trigger workflow execution for procurement approvals?

No, direct HTTP requests are explicitly blocked for workflow execution. You must use skillflaw-cli commands to ensure controlled operations, applying CLI guardrails that validate JSON payloads and mandate tree-based node localization for procurement and approval tasks.

What prerequisites do I need to run skillflaw-cli for HR and reimbursement tasks?

You need prior CLI authentication and configuration, including a valid base URL and API-key authentication. This setup is required before locating project-scoped skills via the tree and validating JSON payloads for HR and reimbursement tasks.

How does node localization work when finding project-scoped skills via the CLI tree?

Node localization works by navigating the skillflaw-cli tree to locate the correct tenant, business, and project context. This ensures you read the generated SKILL.md for the target node, enabling controlled skill discovery without guessing identifiers.

What are the guardrails for ensuring correct JSON payload validation during enterprise automation?

The guardrails enforce required preconditions like API-key authentication, payload validity, and node localization. This ensures correct enterprise automation by validating JSON payloads and restricting operations to CLI commands, preventing bypass of official workflow flows.