Explore skills
Showing 61981–62010 of 77104 skills
Close out a working session: update `docs/progress.md`, report uncommitted and unpushed work, and list the session's decisions and open threads. Read-only on git — never commits, stages, or pushes.
NagareNegishi/DJ-App
Stars: 0Claude CodeCodexApply whenever the task is diagnosing a bug, a failing test, or unexpected behavior — even if the user only says "fix it". Core rule: never fix what has not been reproduced. Not required for feature work, or when the user has already stated the cause and only wants the change made.
NagareNegishi/DJ-App
Stars: 0Claude CodeCodexCore XMTP Agent SDK setup and patterns. Use when creating new agents, handling messages, setting up middleware, or configuring environment variables. Triggers on agent setup, XMTP configuration, message handling, or middleware implementation.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexInteractive button-based UI for XMTP agents following XIP-67. Use when creating menus, confirmation dialogs, selection options, or any button-based interaction. Triggers on inline actions, buttons, menus, or ActionBuilder.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexFile attachment handling for XMTP agents. Use when sending or receiving images, files, or any encrypted remote attachments. Triggers on file upload, image sending, or remote attachment handling.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexPatterns for handling commands, validating input, and filtering messages in XMTP agents. Use when implementing slash commands, validators, or message filters. Triggers on command handling, input validation, or type guards.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexToken transactions and wallet integration for XMTP agents. Use when sending USDC, creating transaction requests, or handling transaction confirmations. Triggers on USDC transfer, wallet calls, or transaction reference.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexGroup conversation management for XMTP agents. Use when creating groups, managing members, setting permissions, or sending welcome messages. Triggers on group creation, member management, or permissions.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexENS and Web3 identity resolution for XMTP agents. Use when resolving domain names, extracting mentions, or fetching Farcaster profiles. Triggers on ENS resolution, Farcaster lookup, or mention extraction.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexEmoji reactions and thinking indicators for XMTP agents. Use when adding reactions to messages or showing processing state with thinking emoji. Triggers on emoji reactions, thinking indicator, or message acknowledgment.
xmtplabs/xmtp-agent-examples
Stars: 53Claude CodeCodexMUST use when configuring schedules.
kma-core/windmill
Stars: 0Claude CodeCodexDisentinel/grafema
Stars: 35Claude CodeCodexUse when the user wants to publish a new agent skill (a directory containing `pyproject.toml` + `src/<pkg>/skill_files/SKILL.md`) to the company's private AWS Agent Registry + CodeArtifact. Walks build → CodeArtifact upload → CreateRegistryRecord → optional submit-for-approval. Requires AWS credentials with codeartifact:PublishPackageVersion and agent-registry:CreateRegistryRecord on the target registry. AWS rejects unauthorized publication. Triggers on phrases like "publish this skill", "register this in our skill registry", "把这个 skill 发布出去", "推到 skills registry".
ericyanpek/agentcore-private-registry-blueprint
Stars: 0Claude CodeCodexManage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
sergiovazquezdml/Base-de-datos-aluminio
Stars: 0Claude CodeCodexProfessional code review with auto CHANGELOG generation, integrated with Codex AI. Use when you want professional code review before commits, you need automatic CHANGELOG generation, or reviewing large-scale refactoring.
sergiovazquezdml/Base-de-datos-aluminio
Stars: 0Claude CodeCodexExactly one of name and title, so exactlyOneOf is satisfied.
hancrafted/markdown-harness
Stars: 0Claude CodeCodexReapply local modifications after a GSD update
Souvik-223/agent-skills-agentic-tools
Stars: 0Claude CodeCodexckdan19/LabNotebook-Summarizer
Stars: 0Claude CodeCodexExtract frames or short clips from videos using ffmpeg.
x402agent/SolanaOS
Stars: 11Claude CodeCodexStart voice calls via the SolanaOS voice-call plugin.
x402agent/SolanaOS
Stars: 11Claude CodeCodexConvenes multiple agents to debate an important decision
Guild-Agents/guild
Stars: 4Claude CodeCodexQA + bugfix cycle until it passes
Guild-Agents/guild
Stars: 4Claude CodeCodexAudit dead code in frontend/src for Svelte frontend code. Triggers on: requests like 'find dead code', 'remove unused code', 'cleanup unused', 'what can be refactored', deeper inspection after a large refactor (bind:event, helper extraction, feature removal), before a big feature update, or after a long merge. Checklist: unused imports, props with no call sites, $state values never read, $derived values never read, functions never called, exports never imported, types/interfaces never used, the $derived(() => expr) anti-pattern, and inline handlers that could be refactored. Produce a report first, then execute.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexAnti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexOverrides 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.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexReview the working tree before committing to Git. Triggers on: the user asks to commit or push, a large task is complete, or a PR is about to be created. Rules: ensure `svelte-check` passes (see the verify-svelte-check skill), use `git status` to inspect all files, use `git diff` for staged and unstaged changes, classify pre-existing versus new changes, match the repo style (see `git log --oneline -10`), do not stage irrelevant files, do not commit secrets, do not amend, and do not force-push.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexManage translations for this Svelte SPA's custom i18n system. Use whenever the user mentions translations, i18n, langStore, t(), adding/translating keys, hardcoded strings, missing translations, language toggle, or the frontend/src/lib/i18n/{en,id}.json files. Triggers on: i18n, translation, translate, t(), langStore, hardcoded string, missing translation, language, bahasa, en.json, id.json, language key, Add [language] translation, is this string translated?
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexUse the Playwright MCP to verify the visual appearance of the site under development. Triggers on: questions about appearance, layout, UX, after editing CSS/tokens or UI components with visual impact, debugging 'why does it look like this', wanting to check interactions (click, scroll, language switch), or wanting a real screenshot. Rule: navigate to the dev server first (usually http://localhost:5173), then act — use snapshot for logical verification and screenshot for visual verification. Always use `wait_for` after navigation before acting.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexCall the `svelte_svelte-autofixer` MCP tool before sending any Svelte code to the user. Triggers on: writing a new component, editing an existing component, refactoring bind/event syntax, $state/$derived/$props/$bindable, extracting inline handlers, snippets that will be sent to the user, or questions like 'why this doesn't work' when the likely answer is Svelte code. Mandatory before replying to the user with a Svelte code block. Cheaper than sending the code to the browser.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodexHow to look up Svelte 5 / SvelteKit docs via MCP. Triggers on: uncertainty about Svelte 5 APIs (runes, $bindable, $derived.by, $state, snippets, lifecycle), wanting to check Svelte runtime behavior, or correcting technical terms before answering. Also check the exact Svelte version first in frontend/package.json. Rule: list sections first, match the use cases, then request documentation in batches. Do not use the heart-of-the-system prompt if the autofixer is sufficient.
HappyRehund/terong-impact-hub
Stars: 0Claude CodeCodex