Index of every page on this site: llms.txt
All skills
paulrberg avatar

/yeet

@c9e5a34
by Paul Bergpaulrberg/agent-skills106 stars
11
Run it yourself

Use for GitHub PR/issue/discussion workflows: create/update PRs, issues, or discussions and post issue or discussion comments; triggers include yeet.

Use this Skill: https://skilld.dev/gh/paulrberg/agent-skills/yeet

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈39 tokens for metadata: the name and description. ≈1.4k when used: this file. ≈16k more on demand in 15 files.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈156 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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. Then read the shared reference sections that the workflow names (posting.md, writing.md, context.md) in one parallel batch.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings4d5 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    This skill provides a professional suite of workflows for managing GitHub contributions, including pull requests, issues, and discussions. It uses the GitHub CLI and local scripts for context retrieval and template rendering, and it includes robust security guidance such as mandatory external-disclosure reviews to prevent data leakage.

  • Socket4d

    No alerts

  • Snyk4d

    Risk: MEDIUM · 1 issue

  • Runlayer9mo

    10/10 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at c9e5a34. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated last month
compatibility
Authenticated GitHub CLI >= 2.97.0
coordination
exempt
effort
high
Other metadata
argument-hint
<create-pr|update-pr|create-issue|update-issue|issue-claude-code|issue-codex-cli|issue-sablier|comment-issue|create-discussion|update-discussion|comment-discussion> [options]
skill-dependencies
[
  "cli-gh"
]

README badge

README badge for paulrberg/agent-skills/yeet