Loading...
Loading...
Found 996 Skills
Check for security risks in Skills/code repositories. When the user wants to check if a skill, GitHub repository, npm package, or local code is safe to download or use. This includes detecting malicious code, malware, key stealing, environment variable modification, suspicious network behavior, and evaluating repository reputation (stars, forks, contributors, age). Use this skill whenever the user mentions checking skills for security risks, scanning repositories for malware, verifying code safety, checking npm packages for threats, or asking if a download is safe.
Use this skill as foundation for git workflows. Use when verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs. Do not use when full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep.
Always-on callable lead pipeline for BDRs: HubSpot lead pull → Apollo phone lookup → Clay waterfall enrichment → HubSpot sync → callable queue. Ensures 50+ daily dials by maintaining verified phone inventory. Runs scheduled Mon & Wed 6:15 AM (between prospect-enrich 6:00 and prospect-refresh 6:30). Use when: 'verify phones', 'phone waterfall', 'callable leads', 'who can I call', 'dial list', 'always have someone to call', 'phone check', 'enrich phones'.
Run Go quality checks via make check with intelligent error categorization and actionable fix suggestions. Use when user requests "run quality checks", "check PR quality", "verify code quality", or "run make check". Use before creating commits or during PR review. Do NOT use for non-Go repositories, repositories without a Makefile, or manual linter invocation.
Run Vitest tests and parse results into actionable output. Use WHEN user needs to run JavaScript/TypeScript tests in a Vitest-configured project, verify test suites pass, or get structured failure reports. Use for "run tests", "vitest", "check if tests pass", or "test results". Do NOT use for Jest/Mocha projects, installing dependencies, writing new tests, or auto-fixing failing assertions.
Manage document verification and review workflows in Glean. Use when verifying document accuracy, listing pending verifications, or sending review reminders.
Gets, checks, and verifies the current UTC date and time for unambiguous temporal reference. Use when starting tasks, verifying temporal context, ensuring date awareness before time-sensitive operations, or when incorrect date assumptions are detected.
Verify documentation coverage and generate missing docs interactively
This skill should be used when a user wants to set up WTF in a new repository, verify their environment is ready, check that GitHub CLI is installed and authenticated, install required gh extensions, or ensure the .github/ISSUE_TEMPLATE/ templates are in place — for example "set up wtf", "run setup", "check my environment", "install wtf templates", "verify everything is configured", "initialize wtf", "onboard to wtf", "first time setup", "configure gh for wtf", "prepare this repo for wtf", "is wtf ready", "get wtf running", or "a new dev joined, set them up". Run once per repo when onboarding, or when a contributor joins the project.
Build, debug, and extend integrations with the EasyPost shipping API. Use this skill whenever the user mentions EasyPost, shipping labels, postage, rate shopping, tracking packages programmatically, customs forms, carrier accounts (USPS/UPS/FedEx/DHL/ePost Global), scan forms, pickups, shipping insurance, or webhooks for shipping events. Also trigger on phrases like "create a shipping label," "buy postage," "rate a parcel," "verify an address," "international shipment," "commercial invoice," "Luma rate shopping," "UPS DAP," "DHL eCommerce," or any task involving the `@easypost/api` Node.js SDK or REST endpoints under `api.easypost.com/v2`. Optimized for Node.js/TypeScript but the REST patterns, field names, and carrier gotchas apply in any language.
Use when building or testing OData queries with dxs odata execute: incremental query development, verifying $select/$expand/$filter clauses, or diagnosing query errors against a Footprint API connection.
Use when a PinMe project (Worker TypeScript) needs to integrate user authentication — creating email/password users, verifying id_tokens, querying user info, or listing users via Identity Platform auth proxy APIs.