to-tickets
Creates tracer-bullet tickets from a plan, specification, or current conversation and publishes them to the configured tracker. Records dependencies as text edges in local per-ticket files or native blocking links in a tracker.
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.Creates tracer-bullet tickets from a plan, specification, or current conversation and publishes them to the configured tracker. Records dependencies as text edges in local per-ticket files or native blocking links in a tracker.
Explains how to create, structure, and configure table of contents files for Microsoft Learn documentation. Covers toc.yml and docfx.json.
Provides guidance for reading, creating, updating, and deleting Todoist data through the td CLI. Includes confirmation requirements for destructive actions.
Provides token optimization practices for cost-effective Claude Code usage. Covers efficient file reading, command execution, output handling, and model selection, with a preference for Bash commands over reading files.
Checks ERC20/ERC721 conformity, more than 20 unusual token patterns, contract composition, owner privileges, and on-chain scarcity. Evaluates protocol handling of nonstandard tokens such as fee-on-transfer, rebasing, missing-return-value, and blocklisted tokens.
Audits TON smart contracts for integer-as-boolean misuse, fake Jetton contracts, and forwarding TON without gas checks. Supports security reviews of FunC contracts.
Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.
Covers toolkit authoring, framework compilation, configuration, and model exposure for backend, frontend, human, provider, and external tools. Supports tool rendering, approval gates, MCP integrations, and troubleshooting tool invocation or result delivery.
Helps identify the capabilities an agent needs and create corresponding tool definitions. Attaches those tools to config variations to enable function calling.
Read the community tools page (https://1f3d9.com/tools) and list what other people have built, one line each. Use when the user asks what tools exist for the city; in Claude Code, the slash form is /1f3d9-citylife:tools.
Finds sequences by accession, gene symbol, or transcript isoform through NCBI and ENA. Prioritizes curated RefSeq records over predicted RefSeq records and GenBank submissions.
Provides expertise in Token-Oriented Object Notation, or TOON, a compact, schema-aware JSON encoding for LLM prompts. The description reports token reductions of approximately 40%.
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