586 skills · sorted by relevance
Turns recurring workflows and proven debugging solutions into reusable skill packages. It creates SKILL.md, a readable overview, and optional supporting examples from a user description or saved project memory, with checks for completeness and portability.
Record recurring setup and workflow problems that a repository can fix, so future contributors can avoid the same friction. Also review existing entries, remove duplicates, prioritize useful fixes, and preserve a history of resolved problems.
Find recurring questions in resolved Plain support tickets that existing knowledge articles do not cover. Draft articles from actual resolutions, avoid previously drafted topics, and open a pull request for human review.
Audits recurring SaaS charges against a subscription register using Plaid data. Reports duplicate tools, unused seats, price increases, upcoming renewals, and unlisted charges in a Slack digest, with suggested actions and a ledger tracking previous findings.
Investigate recurring problems by mapping feedback loops, the cycles through which effects influence their causes. Identify underlying structures, match known patterns, and assess where changes could help and what unintended effects they might produce.
Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.
Analyze recent work history and recurring frustration to identify problems that existing skills or workflows do not address. Receive a ranked shortlist of new skill ideas, with supporting evidence, for deciding what to build next.
Set up one-time reminders and recurring tasks, then inspect, edit, delete, or run saved tasks on request. Supports specific execution dates, time zones, and cron-style schedules that define recurring times.
Review past dsh agent sessions to identify recurring tasks and test proposed skill or memory improvements. This skill guides preview runs, validation on reserved tasks, staged proposals, adoption with backups, and scheduled nightly cycles.
Use past local Codex sessions to propose updates to a selected skill and project memory file. Recurring tasks are replayed, changes are checked on separate validation tasks, and proposals are staged for review before adoption.
Analyze past law course exams for recurring topics, question formats, and hidden issues. Compare those patterns with the current syllabus to suggest study priorities and review time, while clearly marking uncertainty about the upcoming exam.
Execute token swaps, recurring purchases, and STRK staking on Starknet. Use avnu to obtain swap quotes, check prices and rewards, and pay transaction fees in a supported token through its paymaster service.
Guides task delegation to Worker agents, completion handling, and recurring task management. It explains how to register assignments, synchronize task files and results, and choose the relevant procedure when checking worker availability or updating task state.
[omh] Recurring Hermes job on a schedule (cron, digests): design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status. Use when the user says: automation-blueprint, scheduled ops, scheduled operation, scheduled operations, automation blueprint, cron blueprint, cron-ready, recurring ops.
The English summary is being prepared. Showing the original description.
Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.
Create reusable agent skills from recurring tasks, or improve existing ones through test prompts and user feedback. Compare outputs with and without a skill, measure performance, and refine descriptions so skills are invoked for the right requests.
Turn recurring Claude Code tasks into reusable slash commands stored as Markdown files. The guidance covers arguments, file references, tool permissions, shell execution, and plugin integration so commands can run consistent, context-aware workflows.
Review abandoned personal projects through local Git history to identify likely stopping points and recurring patterns. Compare revival candidates, select one worth revisiting, and outline concrete steps from checking whether it still runs to publishing it.
Build a single-screen financial report as a self-contained HTML file. Present revenue, recurring revenue changes, margins, cash runway, charts, profit and loss comparisons, key accounts, and an outlook for monthly, quarterly, or yearly reporting.
Review recent Claude Code chats to identify development strengths, recurring difficulties, and learning priorities. Receive a personalized report with practical recommendations and relevant HackerNews articles, delivered to your own Slack direct messages.
Run Ruflo background workers on a recurring schedule within a Claude Code session. Choose tasks such as security analysis, documentation, or test coverage analysis, check their status, and stop the loop after repeated reports of no new work.
Prepare and privately submit feedback to the Muse team after user approval. It covers missing connections, feature requests, recurring failures, and praise, and helps users view or withdraw reports they have already filed.
Turn a topic into a scripted podcast, audio briefing, or narrated summary delivered as an MP3. Support one or several speakers, generate cover art, and manage recurring episodes or publication to an RSS podcast feed.
Schedule Claude Code cloud agents for recurring tasks or a single future run. Define their instructions, repositories, and service connections, then manage routines, run them immediately, and inspect execution logs when problems occur.