All skills
paulrberg avatar

/yeet

@11c939a
by Paul Bergpaulrberg/agent-skills94 stars
7

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

This session only. Nothing lands on disk.

referencesissue-sablier.md

≈592 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sablier Issue Workflow

Create issues in sablier-labs/* repositories. Labels are always applied (user is org owner). Sablier repos don't use GitHub issue templates.

Validate Prerequisites

See context.md > Auth Validation. The label fetch below is the auth check.

Parse Repository Argument

The first token is the repo name (without org prefix) → sablier-labs/{repo_name}. Remove it from arguments; remaining text is the issue description. Parse --check and handle it per posting.md > Error Handling and Idempotency.

Example: lockup "Bug in cliff streams" → repository = sablier-labs/lockup

Apply Labels

Sablier repos are owner-managed — labels always apply. Follow context.md > Fetch Repo Labels to fetch the live label set once and pick labels semantically. Scope labels (e.g., scope: frontend, scope: evm) are discovered organically from the fetched list for repos that define them — no special-case for command-center.

Generate Title and Body

Title

Clear, concise summary (5-10 words).

Body

Default template:

## Problem

[Extracted from user description]

## Solution

[If provided, otherwise "TBD"]

## Files Affected

<details><summary>Toggle to see affected files</summary>
<p>

- [{filename}](https://github.com/sablier-labs/{repo_name}/blob/main/{path})

</p>
</details>

Use task lists only for genuinely trackable work and tables only for repeated comparable fields. Order items per writing.md > List Ordering. See writing.md > Link Formatting for links. Omit "Files Affected" if no files are specified.

Create the Issue

Run posting.md > External-disclosure Review on the title, body, labels, and attachments before posting. Follow posting.md > Error Handling and Idempotency after any failure; a label or metadata failure never authorizes issue recreation.

gh issue create \
  --repo "sablier-labs/{repo_name}" \
  --title "$title" \
  --body "$body" \
  --label "label1,label2,label3"

Display the verified URL with the ### 🚀 Issue created receipt from SKILL.md.

Examples

# Bug report
lockup "Bug in stream creation for cliff durations"

# Feature request
command-center "Add dark mode toggle to dashboard"

# With --check flag
lockup --check "Support dynamic durations"

# Docs update
docs "Update integration guide for v2.2"

Source: SKILL.md on GitHub

2 warnings5d5 checks · Risk SAFE
  • Gen Agent Trust Hub5d

    The 'yeet' skill provides robust workflows for managing GitHub Pull Requests, issues, and discussions using the GitHub CLI. It implements strong security practices, including a mandatory 'External-disclosure Review' to prevent accidental credential exfiltration and safe YAML parsing for GitHub issue forms. While it processes external data from GitHub, its primary purpose and built-in review gates mitigate risks of indirect prompt injection.

  • Socket5d

    No alerts

  • Snyk5d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    10/10 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

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

Last checked against GitHub yesterday.

Activeupdated 6 days ago
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