KingInYellows
@KingInYellows Organization
Public Skills
agent-native-architecture
by KingInYellows
"Reference for agent-native architecture principles: action parity, context parity, shared workspace, primitives over workflows, and dynamic context injection. Use when authoring agent integrations or designing tool surfaces."
ci-conventions
by KingInYellows
'Shared CI conventions reference (not an executable action) — validation rules, failure patterns (F01-F12), error catalog, and security patterns. Consult when agents or commands need CI-specific validation or pattern-matching reference.'
cursor-delegation
by KingInYellows
Host-neutral reference for the Cursor Cloud Agent delegation lifecycle, the yellow-cursor CLI's JSON contract, and its safety/idempotency rules. Use when building or reasoning about a surface that delegates work to a Cursor Cloud Agent through the CLI.
gt-merge
by KingInYellows
Merge the current stack's pull requests, from trunk up to the current branch, via Graphite. Use when the user says "merge my stack" or "land these PRs" and the stack is fully reviewed and ready.
stack-decomposition-format
by KingInYellows
Structured format contract for "## Stack Decomposition" sections in plan documents, shared by gt-stack-plan (producer) and flow:work (consumer). Use when writing or parsing a Stack Decomposition section.
stack-plan-style
by KingInYellows
Display guidance for presenting a stacked-PR plan — ordered branch tree with intent, commit type, and dependency notes. Use when gt-stack-plan presents a stack plan for user confirmation.
gt-nav
by KingInYellows
Visualize your Graphite stack and navigate between its branches. Use when user says "show my stack", "where am I in the stack", "go up/down a branch", or "checkout the top of the stack". Not for restacking, syncing, or cleanup — use the gt-sync or gt-cleanup skill.
gt-sync
by KingInYellows
Pull latest trunk, restack all tracked branches, and untrack branches whose PRs merged. Use when user says "sync with main", "rebase my stack", or "pull latest", after PRs merge, or when gt reports "needs restack". Not for deleting stale local-only branches — use the gt-cleanup skill.
ci-setup
by KingInYellows
Check CI prerequisites and configure the self-hosted runner SSH config. Use when first installing the plugin, after adding runners, or when CI commands fail with auth or connectivity errors.
ci-conventions
by KingInYellows
Shared CI conventions reference (not an executable action) — validation rules, failure patterns (F01-F12), error catalog, and security patterns. Consult when agents or commands need CI-specific validation or pattern-matching reference.
ci-lint-workflows
by KingInYellows
Lint GitHub Actions workflows for self-hosted runner issues (W01-W14). Use when checking workflows before pushing or finding common CI pitfalls; previews and confirms before applying any fix.
diagnose-ci
by KingInYellows
Reference guide (not an executable action) for CI debugging workflows and the F01-F12 failure-pattern catalog on self-hosted runners. Consult when you need to understand debugging workflows or failure patterns; to actually run a diagnosis, use the ci-diagnose skill instead.
ci-status
by KingInYellows
Show recent CI workflow run status. Use when the user asks for CI status, recent builds, what is running, or needs to find a run ID for diagnosis.
ci-setup-runner-targets
by KingInYellows
Configure runner pool targets, routing rules, and semantic metadata for CI workflow optimization (wizard, YAML import, or GitHub API discovery). Use when setting up runner-aware CI optimization or after changing your runner fleet.
agent-native-architecture
by KingInYellows
"Reference for agent-native architecture principles: action parity, context parity, shared workspace, primitives over workflows, and dynamic context injection. Use when authoring agent integrations or designing tool surfaces."
agent-native-audit
by KingInYellows
Audit checklist for evaluating an existing codebase against agent-native architecture principles to identify parity gaps. Use when auditing for agent-native readiness, before adding a new agent capability, or when triaging agent-behavior regressions.
ce-ideate
by KingInYellows
"Generate and critically evaluate grounded ideas about a topic. Use when asking what to improve, requesting idea generation, exploring surprising directions, or wanting the AI to proactively suggest strong options before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on X', 'surprise me', 'what would you change', or any request for AI-generated suggestions rather than refining the user's own idea."
ce-optimize
by KingInYellows
"Run metric-driven iterative optimization loops. Define a measurable goal, build measurement scaffolding, then run parallel experiments that try many approaches, measure each against hard gates and/or LLM-as-judge quality scores, keep improvements, and converge toward the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation. Inspired by Karpathy's autoresearch, generalized for multi-file code changes and non-ML domains."
ce-agent-native-audit
by KingInYellows
Run comprehensive agent-native architecture review with scored principles
ce-debug
by KingInYellows
'Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says ''debug this'', ''why is this failing'', ''fix this bug'', ''trace this error'', or pastes stack traces, error messages, or issue references.'
ce-doc-review
by KingInYellows
Review requirements or plan documents using parallel persona agents that surface role-specific issues. Use when a requirements document or plan document exists and the user wants to improve it.
ce-agent-native-architecture
by KingInYellows
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
ce-worktree
by KingInYellows
Create an isolated git worktree for parallel feature work or PR review. Use when starting work that should not disturb the current checkout, or when ce-work or ce-code-review offers a worktree option.
ce-compound-refresh
by KingInYellows
Refresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.