tasuku
Agent-first task management. Use when tracking multi-session work, recording learnings/decisions, managing task dependencies, or persisting context across sessions. Provides tk_list, tk_add, tk_done, tk_start, tk_learn, tk_decide, tk_note, tk_show, tk_find, tk_ready, tk_context, tk_stats, tk_block, tk_task, tk_metadata, tk_manage, tk_health, tk_suggest, tk_deps, and tk_help tools.
ss-ship
Quality-gated merge to parent branch (DESTRUCTIVE). ALWAYS confirms on ship/deploy/merge/release intent.
ss-rollback
Safely rollback failed features (DESTRUCTIVE). ALWAYS confirms on rollback/undo/revert/abort intent.
ss-release
Prepare releases with changelog, version bump, and tagging. Confirms on release/tag/publish/version intent.
ss-modify
Modify features with impact analysis and compatibility checks. Triggers on modify/change/update/refactor intent.
ss-metrics
Show feature metrics and sprint analytics. Triggers on metrics/stats/analytics/how-did-we-do intent.
ss-init
Initialize SpecSwarm for a project with constitution and standards. Triggers on setup/initialize/configure intent.
ss-fix
Fix bugs with regression testing and auto-retry. Triggers on fix/debug/broken/error/not-working intent.
ss-build
Spec-driven feature development workflow. Triggers on build/create/add/implement/develop intent.
ss-status
Check build progress and session status. Triggers on progress/status/done/how's-the-build intent.
ss-upgrade
Upgrade deps/frameworks with breaking change analysis. Triggers on upgrade/update/migrate/modernize intent.
madsci-cli
Working with the MADSci CLI (the `madsci` command). Use when adding, modifying, or debugging CLI commands, or when using the CLI to operate a MADSci lab.
madsci-experiments
Working with MADSci experiment modalities and the experiment lifecycle. Use when creating, modifying, or debugging experiments using ExperimentScript, ExperimentNotebook, ExperimentTUI, or ExperimentNode.
quality-checks
Treat type errors, test failures, lint warnings, and coverage gaps as authoritative feedback rather than obstacles. Use when running tests, type checkers, linters, or coverage tools; when tempted to add `# type: ignore`, `# noqa`, `as any`, `@ts-ignore`, `# pragma: no cover`, or to skip/quarantine a test; when deciding how strict to be in an existing codebase; or when designing code that is hard to type or test.
madsci-managers
Working with MADSci manager services (Event, Experiment, Resource, Data, Workcell, Location, Lab). Use when creating, modifying, debugging, or configuring manager servers.
madsci-nodes
Working with MADSci node modules for laboratory instrument integration. Use when creating, modifying, debugging, or testing node modules that interface with scientific instruments.
code-ratchets
Implement code quality ratchets to prevent proliferation of deprecated patterns. Use when (1) migrating away from legacy code patterns, (2) enforcing gradual codebase improvements, (3) preventing copy-paste proliferation of deprecated practices, or (4) setting up pre-commit hooks to count and limit specific code patterns. A ratchet fails if pattern count exceeds OR falls below expected—ensuring patterns never increase and prompting updates when they decrease.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
better-mousetraps
Evaluate build-vs-import decisions before writing new functionality. Use when (1) about to implement non-trivial functionality that likely exists as a library, (2) the user's request could be solved by an existing tool or package, (3) you catch yourself writing utility code (parsing, validation, HTTP, crypto, dates, etc.) that smells like a solved problem, or (4) planning a feature and need to weigh develop-in-house vs. adopt a dependency.
keepachangelog
Maintain `docs/CHANGELOG.md` in the Keep a Changelog 1.1.0 format. Use when adding a CHANGELOG entry for a new feature, bug fix, deprecation, or removal; preparing a release (cutting an `[Unreleased]` section into a versioned section); reviewing a PR for missing or malformed CHANGELOG entries; or whenever the user mentions "changelog", "release notes", "what's new", or "Unreleased" section.
madsci-release-audit
Audit MADSci release artifacts for completeness and correctness. Use when preparing a PR, finishing a plan, completing a feature branch, or before any merge to main/unstable. Checks CHANGELOG, docs, guides, example lab, notebooks, templates, and skills for staleness, broken imports, and deprecated patterns.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
plang
Expert guidance for Plang programming language (plang.is). Use when the user asks about Plang syntax, wants to generate Plang code, needs help debugging Plang goals, wants to understand Plang patterns, or is working on Plang projects. Plang is a natural language pseudo-code language with goal-based architecture using SQLite databases.
submit-forma-reimbursement
Use for submitting Forma reimbursement claims from receipt files.
x-bookmarks
Use when the user wants to read their X (Twitter) bookmarks - tweets they have privately saved. Lists, searches, and exports bookmarks from a connected account. Read-only; requires an account connection.
x-communities
Use when the user wants to read X (Twitter) Communities - the group-focused feature. Pulls community member lists, posts within a community, and searches across communities. Read-only.
x-lists
Use when the user wants to read X (Twitter) Lists. Extracts list members, list followers, and the post feed of a list. Read-only.
x-spaces
Use when the user wants to read X (Twitter) Spaces data - the audio room feature. Extracts Space participants, hosts, speakers, and listeners. Read-only.
x-trends
Use when the user wants to know what is trending on X (Twitter) right now. Fetches current trending topics, hashtags, and volumes by country. Useful for content ideation, timely posts, news monitoring, and spotting viral moments.
x-twitter-scraper
Use when the user needs to interact with X (Twitter) - searching tweets, looking up users/followers, posting tweets/replies, liking, retweeting, following/unfollowing, removing followers, sending DMs, downloading media, monitoring accounts in real time, or extracting bulk data. Provides 112 REST API endpoints, 2 MCP tools, and HMAC webhooks. The skill authenticates only with a Xquik API key (xq_...) and NEVER asks for, transmits, stores, or logs any X account login material - X account connection is done by the user in the Xquik dashboard. Use even if the user says 'Twitter' instead of 'X', or asks about social media automation, tweet analytics, or follower analysis.
for-you-feed
Use when the user wants to read the For You home timeline on X (Twitter) through the API. Surfaces the algorithmic home timeline (cursor-paginated) with an option to suppress already-seen tweets. Read-only.
search-tweets
Use when the user wants to search tweets on X (Twitter) by keyword, phrase, hashtag, from a specific user, within a date range, or with engagement filters. Covers both the live search endpoint (latest matches) and bulk tweet search extractions (up to 1,000 tweets per job). Returns tweet IDs, text, authors, metrics, and timestamps.
post-tweets
Use when the user wants to post a tweet, reply to a tweet, quote tweet, or publish a note tweet (long-form, up to 25,000 characters) on X (Twitter). Handles tweet text, media attachments, reply targeting, community posting, and note tweets. Covers posting actions only - for search, analytics, or monitoring see the related skills.
check-mutuals
Use when the user wants to check mutual follows on X (Twitter) - which accounts follow each other, or which of account A's followers also follow account B. Useful for relationship mapping and social graph analysis. Read-only.
clean-followers
Use when the user wants to audit their X (Twitter) followers for bots, inactive accounts, or ghosts. Analysis-only; removal is not exposed via the API and must be done in the dashboard or X app.
export-tweets-csv
Use when the user wants to export X (Twitter) data to CSV, JSONL, or XLSX. Covers exporting extraction results (tweets, followers, mentions, giveaway entrants) and formatting them for spreadsheets or pipelines. Download handling only.
extract-followers
Use when the user wants to extract the follower list of any public X (Twitter) account. Pulls follower profiles, filters by verified status, and exports to CSV or JSONL for analysis. Read-only.
find-bangers
Use when the user asks for 'bangers' on X (Twitter) - breakout tweets with exceptional engagement relative to the author's usual performance. Surfaces anomalously high-performing tweets for inspiration or trend-spotting. Read-only.
find-influencers
Use when the user wants to find X (Twitter) influencers in a niche. Searches users by bio keyword, filters by follower count and engagement, and surfaces active accounts suited for outreach or partnership research. Read-only discovery.
find-viral-tweets
Use when the user wants to find viral or high-engagement tweets on X (Twitter) around a topic, from a specific author, or across a hashtag. Filters by minimum likes, retweets, or views. Read-only discovery tool.
follow-unfollow
Use when the user wants to follow or unfollow accounts on X (Twitter), or check whether one account follows another. Single-target only; bulk follow operations require explicit per-account confirmation.
send-dms
Use when the user wants to send a direct message on X (Twitter), read DM history with a recipient, or manage their DM inbox. Covers one-to-one DM sends only; no bulk blasting.
going-viral
Use when the user wants to maximize a tweet's chances of going viral on X (Twitter). Combines idea generation, style matching, algorithm scoring, and viral-reference mining into one end-to-end workflow. Advisory; user always confirms the final post.
grow-followers
Use when the user wants a plan to grow their X (Twitter) followers. Analyzes their recent tweets, identifies what worked, suggests content patterns, and recommends posting cadence based on style analysis. Advisory; does not post or follow anyone autonomously.
tweet-ideas
Use when the user wants tweet ideas or content prompts for X (Twitter). Generates a batch of post ideas based on the user's niche, recent trends, and their style profile. Ideation only - drafting and posting are separate skills.
tweet-replies
Use when the user wants to read replies to a specific tweet on X (Twitter). Fetches the reply thread, reply authors, engagement on each reply, and filters for top replies. Read-only; for posting replies see post-tweets.
tweet-style
Use when the user wants to analyze the writing style, voice, or tone of an X (Twitter) account. Extracts stylistic patterns, top topics, format preferences, and engagement profile for a handle. Read-only style analysis.
tweet-analytics
Use when the user wants to check a tweet's engagement metrics - likes, retweets, quotes, replies, bookmarks, impressions, views - or compare engagement across multiple tweets. Fetches per-tweet metrics, lists of users who liked or retweeted, and breakdowns of how a tweet performed. For posting new tweets or searching, use the sibling skills.
Page 735 of 1713 · 85620 results
