Explore skills
Showing 21331–21360 of 77104 skills
Transfer full task ownership to a fresh agent with a verified brief and explicit release. Use for replacing the current executor, including a directly assigned task with no work card; not for supervising a helper.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexSet recurring checks or completion watches with `sno heartbeat` and its persistent log reader. Use for periodic reports or unattended long runs. Not for calendar scheduling or commands watched directly.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexRegister this agent and terminal with Reach for cards, calls and wake-ups. Use when asked to join, connect, or become reachable, or when a manually opened agent lacks `SNO_EXECUTOR_ADDR`.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexQuota-triggered failover from Claude Code, Codex, Cursor, Hermes or OpenClaw. When armed, it reads the sender quota and tries other-vendor models in place, then receiving agents in the configured order. Use when a long run must finish even if one vendor's quota runs out. Not a monitor for anything else.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexRead remaining Claude Code and Codex subscription quota without spending it. Use when the user asks or after a vendor rejects work for quota; a caller such as rotate-agent may also arm a scheduled read on purpose. Never poll on your own; after a `wait` verdict, pass the reset wait to `sno heartbeat` and re-read once when it ends.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexPut two agents on one task: one builds, the other reviews what it built, and they settle the findings between themselves. Use when asked to pair agents, tag-team a task, or have work built and reviewed without the person carrying it between agents. Not for reviewing work that already exists (peer-review) or for passing a task on (handoff).
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexUse when asked about harness9 architecture, module design, or how components interact — explains the system design
ZhangShenao/harness9
Stars: 167Claude CodeCodexFeature auto-development — clarify requirements, generate spec, dispatch dev sub-agent to implement and merge into current branch
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when debugging Go errors, test failures, or unexpected behavior — step-by-step diagnosis approach
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when writing or reviewing Go code — explains harness9 project coding conventions and patterns
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when asked about harness9 architecture, module design, or how components interact — explains the system design
ZhangShenao/harness9
Stars: 167Claude CodeCodexFeature auto-development — clarify requirements, generate spec, dispatch dev sub-agent to implement and merge into current branch
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when debugging Go errors, test failures, or unexpected behavior — step-by-step diagnosis approach
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when writing or reviewing Go code — explains harness9 project coding conventions and patterns
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when the user invokes /pr or asks to push changes and open a pull request, after commits are ready to be pushed to a remote branch and merged into the main branch.
ZhangShenao/harness9
Stars: 167Claude CodeCodexUse when the user wants to evaluate a creator, influencer, or brand audience using public profile signals, TikTok audience demographics, follower/following data, comments, geography, language, and content fit. Helps judge sponsorship and market fit.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexUse when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or voice-of-customer insights from public social posts and videos.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexUse when the user wants to analyze a creator, influencer, founder, or brand social account and understand positioning, content pillars, outlier posts, hooks, format choices, audience reaction, and what can be copied or tested.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexUse when the user wants to find creators, influencers, affiliates, or social accounts in a niche for outreach, partnerships, sponsorships, UGC, seeding, or competitive research. Produces scored prospect lists from public social data.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexUse when the user wants to validate a product idea, find pain points, mine demand signals, discover objections, or gather voice-of-customer language from Reddit, social posts, video transcripts, and comments. Produces evidence-backed product research.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexScrape and extract public data from 27+ social media platforms using the ScrapeCreators REST API. Covers TikTok, Instagram, YouTube, LinkedIn, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, Snapchat, Twitch, Kick, Truth Social, TikTok Shop, Google, and link-in-bio services (Linktree, Komi, Pillar, Linkbio, Linkme, Amazon Shop). Use when the user asks to scrape, fetch, extract, search, or look up social media profiles, posts, videos, reels, comments, transcripts, followers, ads, hashtags, trending content, or engagement metrics from any social platform. Also use when user mentions ScrapeCreators, social media API, ad library, or creator data.
ScrapeCreators/social-media-research-skills
Stars: 6.6kClaude CodeCodexDiagnose a failed CI workflow run and fix it the /snag way. A tested read-only script fetches the run, reports every failed job and step with the log region around its errors (not the post-job cleanup), and classifies each against this repo's gates.tsv, printing the banner a gate carries when its obvious fix is the wrong one. Then: re-run only what is transient, reproduce locally, find the root cause, and show one decision screen; the chosen fix is built test-first and committed on a fix branch, never pushed. Use when a CI run failed on a pull request or on the default branch.
jellyrock/jellyrock
Stars: 52Claude CodeCodexDEPRECATED, replaced by the `enrich` phase built into /crash-report. The old flow filed crash issues first and enriched them one by one afterward. The new flow (stage, then enrich, then file) pulls the dashboard backtrace before filing, so issues are born complete and architectural-class crashes go to their epic instead of becoming standalone issues. Do not invoke it for new work: run /crash-report and paste the backtraces during its enrich step. It stays only as a redirect; the `enrich-issue` script subcommand still exists as a legacy escape hatch for a crash issue filed before the change.
jellyrock/jellyrock
Stars: 52Claude CodeCodexDraft a GitHub issue body for the JellyRock repo from a Reddit/Discord post or free-form bug report and submit it via forge.sh. Reads the YAML form templates under .github/ISSUE_TEMPLATE/ to know which fields are required, fills them by extracting from the input, asks for any missing required fields, validates the body matches the chosen template's schema, then runs forge.sh issue create with the auto-labels the template defines. Use when you have a user report (paste from anywhere) and want to formalize it into a properly-structured GitHub issue.
jellyrock/jellyrock
Stars: 52Claude CodeCodexThis skill should be used when the user explicitly types "/end-session": the mandatory final step of any session started or resumed with /start-project or /resume-project, which the agent prints alone in its own block as the session's last line for the user to type, never invoking it directly. It updates the active project's PLAN.md (Status, kickoff, log), checks the PLAN against itself, and commits+pushes. Do not auto-invoke on vague phrases mid-session.
jellyrock/jellyrock
Stars: 52Claude CodeCodexInvestigate one GitHub issue and act on it the /snag way. Fetches the issue and its comments, first checks it is still true (everything it names still exists), reads it through the repo's issue forms, classifies it (bug, feature, enhancement, or a design decision), checks whether it is real, reproducible and not already fixed, maps it to an area, reproduces it and finds the root cause, then shows one decision screen; the chosen fix is built test-first and committed on a fix branch, never pushed. Anything posted on the issue is drafted and shown first. Use when you have an issue number you want to act on.
jellyrock/jellyrock
Stars: 52Claude CodeCodexGuided workflow for standing up a new Jellyfin apiVersion tier (V3, V4, …) in JellyRock when an upstream release restructures the API enough to need a new `if m.getApiVersion() >= N` dispatch level. Wraps the "Add an API tier" recipe in docs/dev/jellyfin-server-versioning.md and walks every surface that must move together (the boundary map in YAML, its BrightScript twin `resolveApiVersion()`, the `sdkVN.bs` endpoints, the dispatch branches, the device profile, the manifest tier clamp, and the validators), stopping at each step so the tier split cannot land half-built. Use when proactive RC/master triage (via `/server-upgrade <rc-or-unstable>`) shows a breaking API shift that a per-method `>= N` branch must cover. Not for routine endpoint additions inside an existing tier (those use the existing `>= 2` shape directly).
jellyrock/jellyrock
Stars: 52Claude CodeCodexGuided workflow for writing a registry migration in JellyRock when a setting key is renamed, removed, or its data shape changes. Walks docs/dev/registry-migrations.md (add a version constant, add a guarded block to the runner for the right scope in source/migrations.bs, update the code that used the old name, write a real-registry integration test, run it on hardware). Use when an existing setting changes shape; brand-new settings don't need migrations and should use /new-setting instead.
jellyrock/jellyrock
Stars: 52Claude CodeCodexGuided workflow for adding a new user setting or global setting to JellyRock. Walks the recipe in docs/dev/new-user-setting.md (pick the kind, add the settings/settings.json entry, add its strings, add the JellyfinUserSettings field, read it in code, test it). Stops at each step to verify and gives the user the relevant file paths. Use when adding a toggle, a choice, a number or a text setting that the user can change in the JellyRock Settings screen.
jellyrock/jellyrock
Stars: 52Claude CodeCodexCreate or update a pull request: a typed title (`fix:`, `feat:` … from `scripts/lib/pr-title.js`, which places the change in CHANGELOG.md), category labels chosen by judgment, a concise body from `.github/pull_request_template.md` that reads as the squash commit message, and one skill-owned "review notes" comment for the detail reviewers want but `git log` doesn't. Detects an existing open PR for the current branch and routes to update-mode (diff title/labels/body/comment, ask, then apply) instead of duplicating; aborts cleanly on merged/closed PRs. Scans branch + commits for related issues, falls back to `gh` issue search, surfaces architecture docs whose related-files were touched, and runs the four-pillar judgment passes (tech-debt scan, decision-shape detect, followup capture) so journal hygiene is part of shipping rather than a separate manual step. Required for all PRs in this repo; it supersedes any default PR-creation flow.
jellyrock/jellyrock
Stars: 52Claude CodeCodex