yeet
Use for GitHub PR/issue/discussion workflows: create/update PRs, issues, or discussions and post issue or discussion comments; triggers include yeet.
- Installs
- 2.6K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/paulrberg/agent-skills --skill yeet- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads yeet automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
GitHub Contribution Workflows
This skill is coordination-exempt: skip the ai-coord gate for its declared work.
Create or update GitHub contributions from repository evidence, using the matching workflow's templates, idempotency rules, and Paul's writing voice.
Prerequisites
Use the first required read-only gh command in each workflow to validate authentication. Resolve <skill-dir> once to
the absolute directory containing this SKILL.md.
This skill, rather than the target repository, bundles the yeet-context.sh helper. Invoke it as
<skill-dir>/scripts/yeet-context.sh. Never search for it in the target repository. Prefer the helper when the workflow
needs repository, template, discussion, label, or issue/PR thread context.
For YAML issue forms, invoke <skill-dir>/scripts/issue-form.py. inspect fetches and normalizes the selected live
form. render validates answers keyed by field ID and produces the exact Markdown body plus posting metadata. The
helper never selects a template, writes answers or titles, performs an external-disclosure review, or posts externally.
All issue creation and update workflows apply references/context.md > Issue Metadata Permissions before resolving or
passing metadata. Rendered template metadata describes requested values, not the viewer's authority to apply them.
For pull request workflows, also verify:
- Working tree is clean or changes are committed
- Current branch has commits ahead of the base branch
- Remote tracking is configured
Use cli-gh for GitHub reads, workflow automation, or command syntax that is not part of authoring and posting a
contribution.
Workflows
Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent.
| Workflow | Trigger | Reference |
|---|---|---|
| Create PR | "create PR", "open PR", "yeet a PR" | references/create-pr.md |
| Update PR | "update PR", "edit PR" | references/update-pr.md |
| Create Issue | "create issue", "file issue" (generic repo) | references/create-issue.md |
| Update Issue | "update issue", "edit issue", "relabel issue" | references/update-issue.md |
| Claude Code Issue | "Claude Code issue", "report bug in CC" | references/issue-claude-code.md |
| Codex CLI Issue | "Codex issue", "report bug in Codex" | references/issue-codex-cli.md |
| Sablier Issue | "Sablier issue", "sablier-labs issue" | references/issue-sablier.md |
| Comment on Issue | "comment on issue", "reply on issue", "post a comment" | references/comment-issue.md |
| Create Discussion | "create discussion", "start discussion" | references/create-discussion.md |
| Update Discussion | "update discussion", "edit discussion" | references/update-discussion.md |
| Comment Discussion | "comment on discussion", "reply on discussion", "edit discussion comment" | references/comment-discussion.md |
Each workflow reference links only the shared context, writing, or posting guidance it needs. Every authored body or comment must follow posting.md > Model Co-signature. When the user requested creation or update, post directly. Do not add a confirmation gate. After a failed write, run the linked idempotency check before any retry.
Never check an external template attestation unless repository or user evidence verifies it. If a required attestation or field cannot be verified, ask for that missing fact rather than inventing agreement. Agent-status decoration belongs outside the authored contribution. Add emoji to a PR, issue, discussion, or comment only when the user's content or the thread's register calls for it.
Completion
The workflow is complete when the requested contribution exists in its final authored state and the returned GitHub URL is verified. For updates/comments, report the changed artifact once. Determine the outcome from readback, not the command's exit status: creation can succeed before a metadata mutation fails.
Use ### 🚀 <artifact> created, ### ✅ <artifact> updated, ### ✅ Comment posted, or ### ✅ Comment updated,
followed by one Markdown link containing the repository, number, and title or action. Add a compact field list only when
base, draft state, reviewers, labels, or changed fields matter. For verified partial success, report the created or
updated artifact and identify omitted or failed metadata.
Use ### ⛔ <artifact> not <action> only for confirmed noncompletion. If readback is inconclusive, report the outcome
as unverified. Include the concrete error, idempotency result, and next action. Keep gh output, JSON, diagnostics,
template fields, URLs, and authored contribution text exact and undecorated.
FAQ
What does the yeet skill do?
Use for GitHub PR/issue/discussion workflows: create/update PRs, issues, or discussions and post issue or discussion comments; triggers include yeet.
How do I install yeet?
Run npx skills add https://github.com/paulrberg/agent-skills --skill yeet in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/yeet/ (personal) or .claude/skills/yeet/ (project).
Which AI agents can use yeet?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is yeet safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains yeet?
It is published by paulrberg in paulrberg/agent-skills. It has 2,583 recorded installs.
More from paulrberg/agent-skills
effect-ts
paulrberg/agent-skills
Use for nontrivial Effect 4 work including services/layers, typed errors, Schema/JsonSchema, Config, runtime/concurrency, @effect/vitest, effect/ai and @effect/ai-, effect/sql and @effect/sql-, Effect Atom (@effect/atom-), or @prb/effect-next.
tailwind-css
paulrberg/agent-skills
Use for Tailwind v4 styling: add/fix classes, configure or migrate Tailwind, use tailwind-variants, or tw-animate-css.
cli-gh
paulrberg/agent-skills
Use for GitHub CLI automation: repository reads, workflow runs, search, codespaces, releases, configuration, or gh command syntax. Use yeet for contribution writes to PRs, issues, comments, or discussions.
code-polish
paulrberg/agent-skills
Polish changed code when the user explicitly asks, or when an active workflow requests post-implementation simplification and risk-profiled review over a fixed file scope.
bump-release
paulrberg/agent-skills
Cut a release: bump versions, write changelogs, commit, tag.
bump-deps
paulrberg/agent-skills
Use for dependency updates: bump npm/pnpm/yarn/bun packages, check outdated, or run taze.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available