Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Cut a new timepicker-ui release. Use when the user wants to bump the version, prepare a release, write/update the changelog, or sync version + changelog across README, CHANGELOG.md and the docs-app (changelog/what's-new/version strings). Drives the build-release subagent in an audit → approve → apply flow, then runs a sanity build. Does NOT git-commit/tag or npm-publish — proposes those for the us…
Coordinates the barwise release sequence across version bumps, tagging, and GitHub releases that build downloadable artifacts. Covers workspace dependency references, SERVER_VERSION synchronization, and tutorial regeneration needed to avoid CI failures.
Create a new zen-ui release with proper version bump, build, tag, and GitHub release with HACS-compatible asset. Use when the user says "make a release", "cut a release", "bump version", "publish a new version", "release X.Y.Z", or anything about releasing/publishing zen-ui.
Prepare code for merge or release with verification, docs, environment, and deployment checks.
Use when verifying a feature pipeline is ready to close and release. Checks all lanes — tests passing, security audit complete, docs synced, ledger has no open blockers — and produces a Go / No-Go decision with evidence.
Helps choose outcome and UX metrics for student app releases and establish baselines, targets, and a review cadence. Uses release success measurements to inform whether to iterate or scale after launch.
Turn raw Lumen release content (a dump of the LedgerHQ/lumen GitHub Releases page) into one minimalist Slack announcement, drafted to lumen-releases. Use whenever the user pastes one or more @ledgerhq/lumen- package releases, a chunk of the Releases page, or asks to "announce", "format", "post", or "write release notes / a Slack message" for new Lumen versions. Trigger it even when the user ju…
Use when generating or editing an Nx version plan in .nx/version-plans/ — the bump type must always be patch, one package per file.
Generates specific, implementable fixes for every finding in findings.json. Produces code patches (unified diff), configuration changes, dependency updates, and IaC fixes — not generic advice but actual before/after code. Uses the reproduction command from each finding as the verification step: "run this after the fix — it should now fail." Stores remediation data in findings.json so the dashboar…
Discipline for repairing a false claim once it has propagated: select what depends on it, produce a replacement, and accept with an expiring verdict. Trigger when: - A claim, citation, premise, or documented fact is found wrong and its downstream consequences must be traced and fixed. - A refutation, a failed re-run, a retracted external source, or a human correction lands against something al…
Schedules reminders for tasks, appointments, and habits using cron jobs and systemEvents. Supports listing, repeating, and deleting reminders, with delivery through session messages or notifications.
Set up 3 remote control modes for Claude Code CLI — local iTerm pair hacking, Discord bot for mobile control, and tmux multi-pane multi-target workflows. Includes dangerouslySkipPermissions security hardening. Based on Critical Thinking Bug Bounty Podcast Episode 166.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name