Source profileQuality 86/100
PaulRBerg/agent-skills/skills/yeet/SKILL.md
yeet
Use for GitHub PR/issue/discussion workflows: create/update PRs or issues, post comments, start discussions; triggers include yeet.
- Source repository stars
- 68
- Declared platforms
- 0
- Static risk flags
- 1
- Last source update
- 2026-08-04
- Source checked
- 2026-08-04
Decision brief
What it does—and where it fits
This skill is coordination-exempt: skip the ai-coord gate (git status / ai-coord status / ai-coord start) for this skill's own work.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/PaulRBerg/agent-skills --skill "skills/yeet"Safe inspection promptEditorial
Inspect the Agent Skill "yeet" from https://github.com/PaulRBerg/agent-skills/blob/2c47aa0b01d513aaa36e0c8271cc8c524734eaee/skills/yeet/SKILL.md at commit 2c47aa0b01d513aaa36e0c8271cc8c524734eaee. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Prerequisites
Use the first required read-only gh command in each workflow as authentication validation. The scripts/yeet-context.sh helper is bundled with this skill, not the target repository. Resolve it to an absolute path relative to the directory containing this SKILL.md, and never searc…
Working tree is clean or changes are committedCurrent branch has commits ahead of the base branchRemote tracking is configured - 02
Workflows
Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent.
Each workflow is fully documented in its reference file. Load the appropriate reference based on user intent.Each workflow reference links only the shared context, writing, or posting guidance it needs. Post directly when the user requested creation or update; do not add a confirmation gate. After a failed write, run the linke…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… - 03
Completion
Complete when the requested contribution exists in its final authored state and the returned GitHub URL has been verified. For updates/comments, report the changed artifact once; for failures, report the idempotency check and next action without claiming a write succeeded.
Complete when the requested contribution exists in its final authored state and the returned GitHub URL has been verified. For updates/comments, report the changed artifact once; for failures, report the idempotency che…Use 🚀 created, ✅ updated, or ✅ Comment posted, 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 f…
Permission review
Static risk signals and limitations
Writes files
The documentation asks the agent to create, modify, or delete local files.
Create or update GitHub contributions from repository evidence, using the matching workflow's templates, idempotencyWrites files
The documentation asks the agent to create, modify, or delete local files.
| Create Issue | "create issue", "file issue" (generic repo) | `references/create-issue.md` |Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 86/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 68 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- PaulRBerg/agent-skills
- Skill path
- skills/yeet/SKILL.md
- Commit
- 2c47aa0b01d513aaa36e0c8271cc8c524734eaee
- License
- MIT
- Collected
- 2026-08-04
- Default branch
- main
View the original SKILL.md
GitHub Contribution Workflows
This skill is coordination-exempt: skip the ai-coord gate (git status / ai-coord status / ai-coord start) for this
skill's own 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 as authentication validation. The
scripts/yeet-context.sh helper is bundled with this skill, not the target repository. Resolve it to an absolute path
relative to the directory containing this SKILL.md, and 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, resolve scripts/issue-form.py the same way. 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 privacy review, or posts externally.
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 |
Each workflow reference links only the shared context, writing, or posting guidance it needs. Post directly when the user requested creation or update; 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
Complete when the requested contribution exists in its final authored state and the returned GitHub URL has been verified. For updates/comments, report the changed artifact once; for failures, report the idempotency check and next action without claiming a write succeeded.
Use ### 🚀 <artifact> created, ### ✅ <artifact> updated, or ### ✅ Comment posted, 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. On failure, lead with ### ⛔ <artifact> not <action>, then state the attempted
target, concrete error, idempotency result, and next action. Keep gh output, JSON, diagnostics, template fields, URLs,
and authored contribution text exact and undecorated.
Alternatives