beautify-decoration
Iterates on the visual identity of a top-down pixel-art decoration (sprite + layout integration) in pixtuoid. Use when…
@ivanwng97Install SkillDevelopment
Skill
/add-source
Wires a new agent CLI into pixtuoid so its sessions become office sprites, from the upstream facts through a reviewed PR. Use when adding support for a CLI, adding a source for a tool, or integrating a coding agent, in a maintainer's session or a contributor's fork. Covers the
Claude Code
$ npx -y skills add pixtuoid/pixtuoid --skill add-source --agent claude-code
Codex
$ npx skills add pixtuoid/pixtuoid --skill add-source -a codex -y
Cursor
$ npx skills add pixtuoid/pixtuoid --skill add-source -a cursor -y
Gemini CLI
$ npx skills add pixtuoid/pixtuoid --skill add-source -a gemini-cli -y
GitHub Copilot
$ npx skills add pixtuoid/pixtuoid --skill add-source -a github-copilot -y
OpenCode
$ npx skills add pixtuoid/pixtuoid --skill add-source -a opencode -y
Windsurf
$ npx skills add pixtuoid/pixtuoid --skill add-source -a windsurf -y
SKILL.md
add-source.SKILL.mdname: add-source
description: "Wires a new agent CLI into pixtuoid so its sessions become office sprites, from the upstream facts through a reviewed PR. Use when adding support for a CLI, adding a source for a tool, or integrating a coding agent, in a maintainer's session or a contributor's fork. Covers the cross-crate checklist, including what a diff-scoped edit silently misses: the site manifest, the per-source badge hue, the home-dir fn and the integration goldens a `--lib` run never builds."
add-source
Copy this list into your plan and work it in order, fixing and rerunning each check until it passes.
- [ ] **Upstream facts.** Answer [the checklist](../../../docs/CONTRIBUTING.md#adding-a-new-agent-cli)'s
step 1 before any code, from the latest release's source. Its questions have no test, so a wrong answer ships green.
- [ ] **The rest of that checklist**, with the test steps in
[`tests/AGENTS.md`](../../../crates/pixtuoid-core/tests/AGENTS.md).
- [ ] **`just test`, never `--lib` alone.** The `sources --json` golden (`cli_json`)
and the `wire_to_pixels` matrix are integration binaries a `--lib` run skips: kimi's PR (#692) passed `--lib` and a multi-lens review with both red.
- [ ] **`just gen-contract`**, only if the `--json`/`SourceStatus`/`OutcomeRow` shape
changed; adding a row doesn't change it.
- [ ] **[The must-run](../../../REVIEW.md#must-run)**: `just hermetic <source>`, or a
live run for a `NOT_HERMETIC` source. Either way the real CLI, never a capture rig's flags.
- [ ] **The org's local-review skill** ([AGENTS.md](../../../AGENTS.md#org-rules)), always: a fork's PR gets no CI
review, so this is its only one. Fold what it finds into one commit.
- [ ] **The PR body** holds step 1's answers and what
[the merge gate](../../../docs/CONTRIBUTING.md#the-merge-gate) asks of it. CI runs the tests.
Read more
name: add-source description: "Wires a new agent CLI into pixtuoid so its sessions become office sprites, from the upstream facts through a reviewed PR. Use when adding support for a CLI, adding a source for a tool, or integrating a coding agent, in a maintainer's session or a contributor's fork. Covers the cross-crate checklist, including what a diff-scoped edit silently misses: the site manifest, the per-source badge hue, the home-dir fn and the integration goldens a `--lib` run never builds."
add-source
Copy this list into your plan and work it in order, fixing and rerunning each check until it passes.
- [ ] **Upstream facts.** Answer [the checklist](../../../docs/CONTRIBUTING.md#adding-a-new-agent-cli)'s
step 1 before any code, from the latest release's source. Its questions have no test, so a wrong answer ships green.
- [ ] **The rest of that checklist**, with the test steps in
[`tests/AGENTS.md`](../../../crates/pixtuoid-core/tests/AGENTS.md).
- [ ] **`just test`, never `--lib` alone.** The `sources --json` golden (`cli_json`)
and the `wire_to_pixels` matrix are integration binaries a `--lib` run skips: kimi's PR (#692) passed `--lib` and a multi-lens review with both red.
- [ ] **`just gen-contract`**, only if the `--json`/`SourceStatus`/`OutcomeRow` shape
changed; adding a row doesn't change it.
- [ ] **[The must-run](../../../REVIEW.md#must-run)**: `just hermetic <source>`, or a
live run for a `NOT_HERMETIC` source. Either way the real CLI, never a capture rig's flags.
- [ ] **The org's local-review skill** ([AGENTS.md](../../../AGENTS.md#org-rules)), always: a fork's PR gets no CI
review, so this is its only one. Fold what it finds into one commit.
- [ ] **The PR body** holds step 1's answers and what
[the merge gate](../../../docs/CONTRIBUTING.md#the-merge-gate) asks of it. CI runs the tests.
5563 skills
Stars on GitHub
Momentum
- stars in total
- 556
Other skills on pixtuoid.
@ivanwng97Install Skilllocal-review
Runs pixtuoid's review locally at either scope — a DIFF review (REVIEW.md with the CI review's own reviewers, plus the must-run…
@ivanwng97Install SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about add-source.
- Which coding agents can use add-source?
- add-source installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.