add-resource-skill

Name: add-resource-skill
Author: pixee

31stars12forks

How to install add-resource-skill?

pixee/pixee-cli/add-resource-skill

$npx -y skills add pixee/pixee-cli --skill add-resource-skill

Installs into the current project.

Summary

Authors a new skills.sh-formatted skill for the pixee CLI under skills/pixee-<noun>/SKILL.md. Trigger on requests like "add a resource skill", "write a skill for pixee X", "author a pixee skill", or "publish a skill for the new Y subcommand". Captures pixee-specific conventions (

Files · 1

View on GitHub

SKILL.md

1	# Author a Pixee CLI Resource Skill
2
3	Guided authoring of a new skill under `skills/pixee-<noun>/SKILL.md`. This repo distributes the skills that teach coding agents (Claude Code, Codex, others) to drive the `pixee` binary. Consistency across siblings is load-bearing for discoverability and the skills.sh install picker.
4
5	For general skill-writing fundamentals (what a SKILL.md is, progressive disclosure, how triggering works), invoke `/plugin-dev:skill-development` first if available. This skill layers pixee conventions on top; it does not repeat them. If that plugin is not installed, a one-paragraph refresher: a SKILL.md is a Markdown file with YAML frontmatter; the `description` field is how the model decides to invoke it, so it must enumerate concrete trigger phrases; keep the body scannable with clear H2 sections; front-load the most common use case.
6
7	## Pixee context you must know
8
9	- Skills modularize around sub-commands. One skill per top-level `pixee <subcommand>` plus a single shared prerequisite skill (`pixee-shared`) that every domain skill references. This keeps each skill scoped to what an agent needs for one command group, and lets the install picker present a small menu of composable pieces.
10	- Install channel. Skills are fetched by agents via `npx skills add pixee/pixee-cli --all` (or the interactive picker without `--all`). A picker-breaking `description` silently drops the skill from the picker.
11	- Release cadence. Skill iteration is decoupled from `pixee` binary releases — revise a skill without waiting for the next CLI tag, and ship a subcommand now and its skill later if the surface isn't finalized.
12	- `pixee-shared` is a hard prerequisite for every domain skill. It covers global flags, exit codes, error rendering, and token security.
13	- `pixee-api` is the canonical HAL reference. Cross-reference it for discovery guidance. Never restate HAL. Never embed OpenAPI specs or long JSON schemas.
14
15	## Before you author
16
17	The `pixee` binary on PATH is the authoritative source for what a skill should teach. Everything in the skill you write must be something you've seen the binary actually do.
18
19	1. Study the CLI by invoking it. Start with `pixee --help` for the top-level surface; then `pixee <subcommand> --help` and each nested `pixee <subcommand> <verb> --help`. Run realistic invocations end-to-end: try each flag, observe exit codes, run `--output text` and `--output json` against the same call to see the shape difference, and follow HAL links with `pixee api <href>` where the endpoint exposes them. Do not document flags or behaviors you haven't seen the binary produce.
20	2. Read two files in full: `skills/pixee-shared/SKILL.md` (every domain skill references it) and the single sibling closest to the new domain — the skill whose H1 shape you will copy. For a command-backed list/CRUD surface, `pixee-repo` (single verb) or `pixee-workflow` (subcommand-per-variant) is almost always the right reference.
21	3. Decide the slot. New `pixee-<noun>` skill versus extending an existing one. Prefer extension when the new surface is fewer than three subcommands and lives naturally inside an existing skill's H1 (e.g., a new `pixee api --new-flag` belongs in `pixee-api`, not a new skill).
22
23	## Naming rules
24
25	- Slug is `pixee-<noun>` in kebab-case, where `<noun>` is a top-level subcommand or a cross-cutting concern (`shared` is the only current exception). Non-command cross-cutting slugs need discussion before landing.
26	- Directory layout: `skills/pixee-<noun>/SKILL.md` — single file. No `references/` sidecar unless the skill exceeds ~150 lines; inline is the default.
27	- The H1 matches the command surface (`# pixee workflow`) or the skill name (`# Pixee CLI — Shared Reference`).
28
29	## Frontmatter template
30
31	Copy this exactly and fill in the angle-bracket placeholders:
32
33	```yaml
34	---
35	name: pixee-<noun>
36	description: "<verb-first, 100-130 chars, no colons, em-dashes, or parens>"
37	metadata:
38	version: 1.0.0
39	openclaw:
40	category: "developer-tools"
41	requires:
42	bins:
43	- pixee
44	cliHelp: "pixee <subcommand> --help"
45	---
46	```
47
48	The `description` has a triple constraint, each one load-bearing:
49
50	- (a) Verb-first, bare infinitive. Existing descriptions start with `Describe`, `Store`, `Send`, `List`, `List, create, and delete`. Match the shape — this is what the skills.sh picker rende

People who liked this also viewed

6 picks

Type

add-resource-skill

31stars12forks

View on GitHub

How to install add-resource-skill?

pixee/pixee-cli/add-resource-skill

$npx -y skills add pixee/pixee-cli --skill add-resource-skill

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Author a Pixee CLI Resource Skill
2
3	Guided authoring of a new skill under `skills/pixee-<noun>/SKILL.md`. This repo distributes the skills that teach coding agents (Claude Code, Codex, others) to drive the `pixee` binary. Consistency across siblings is load-bearing for discoverability and the skills.sh install picker.
4
5	For general skill-writing fundamentals (what a SKILL.md is, progressive disclosure, how triggering works), invoke `/plugin-dev:skill-development` first if available. This skill layers pixee conventions on top; it does not repeat them. If that plugin is not installed, a one-paragraph refresher: a SKILL.md is a Markdown file with YAML frontmatter; the `description` field is how the model decides to invoke it, so it must enumerate concrete trigger phrases; keep the body scannable with clear H2 sections; front-load the most common use case.
6
7	## Pixee context you must know
8
9	- Skills modularize around sub-commands. One skill per top-level `pixee <subcommand>` plus a single shared prerequisite skill (`pixee-shared`) that every domain skill references. This keeps each skill scoped to what an agent needs for one command group, and lets the install picker present a small menu of composable pieces.
10	- Install channel. Skills are fetched by agents via `npx skills add pixee/pixee-cli --all` (or the interactive picker without `--all`). A picker-breaking `description` silently drops the skill from the picker.
11	- Release cadence. Skill iteration is decoupled from `pixee` binary releases — revise a skill without waiting for the next CLI tag, and ship a subcommand now and its skill later if the surface isn't finalized.
12	- `pixee-shared` is a hard prerequisite for every domain skill. It covers global flags, exit codes, error rendering, and token security.
13	- `pixee-api` is the canonical HAL reference. Cross-reference it for discovery guidance. Never restate HAL. Never embed OpenAPI specs or long JSON schemas.
14
15	## Before you author
16
17	The `pixee` binary on PATH is the authoritative source for what a skill should teach. Everything in the skill you write must be something you've seen the binary actually do.
18
19	1. Study the CLI by invoking it. Start with `pixee --help` for the top-level surface; then `pixee <subcommand> --help` and each nested `pixee <subcommand> <verb> --help`. Run realistic invocations end-to-end: try each flag, observe exit codes, run `--output text` and `--output json` against the same call to see the shape difference, and follow HAL links with `pixee api <href>` where the endpoint exposes them. Do not document flags or behaviors you haven't seen the binary produce.
20	2. Read two files in full: `skills/pixee-shared/SKILL.md` (every domain skill references it) and the single sibling closest to the new domain — the skill whose H1 shape you will copy. For a command-backed list/CRUD surface, `pixee-repo` (single verb) or `pixee-workflow` (subcommand-per-variant) is almost always the right reference.
21	3. Decide the slot. New `pixee-<noun>` skill versus extending an existing one. Prefer extension when the new surface is fewer than three subcommands and lives naturally inside an existing skill's H1 (e.g., a new `pixee api --new-flag` belongs in `pixee-api`, not a new skill).
22
23	## Naming rules
24
25	- Slug is `pixee-<noun>` in kebab-case, where `<noun>` is a top-level subcommand or a cross-cutting concern (`shared` is the only current exception). Non-command cross-cutting slugs need discussion before landing.
26	- Directory layout: `skills/pixee-<noun>/SKILL.md` — single file. No `references/` sidecar unless the skill exceeds ~150 lines; inline is the default.
27	- The H1 matches the command surface (`# pixee workflow`) or the skill name (`# Pixee CLI — Shared Reference`).
28
29	## Frontmatter template
30
31	Copy this exactly and fill in the angle-bracket placeholders:
32
33	```yaml
34	---
35	name: pixee-<noun>
36	description: "<verb-first, 100-130 chars, no colons, em-dashes, or parens>"
37	metadata:
38	version: 1.0.0
39	openclaw:
40	category: "developer-tools"
41	requires:
42	bins:
43	- pixee
44	cliHelp: "pixee <subcommand> --help"
45	---
46	```
47
48	The `description` has a triple constraint, each one load-bearing:
49
50	- (a) Verb-first, bare infinitive. Existing descriptions start with `Describe`, `Store`, `Send`, `List`, `List, create, and delete`. Match the shape — this is what the skills.sh picker rende

People who liked this also viewed

6 picks

Type