Total 50,611 skills, Tools & Utilities has 8227 skills
Showing 12 of 8227 skills
Query and trade on Polymarket prediction markets - check odds, trending markets, search events, view order books, place trades, and manage positions.
Interact with Jira and Confluence via the `acli` CLI tool (Atlassian CLI). Use this skill whenever the user wants to manage Jira work items (create, edit, transition, search, comment, assign, bulk ops), manage sprints or boards, list/view Jira projects, or work with Confluence pages, blogs, and spaces — all from the terminal without opening a browser. Also trigger when the user says things like "ดู issue ของฉัน", "transition ไป In Progress", "สร้าง bug ใน Jira", "search ด้วย JQL", "ดู sprint ปัจจุบัน", "bulk transition", "ดู Confluence page", หรือ อะไรก็ตามที่ต้องการโต้ตอบกับ Atlassian products ผ่าน command line. Always use `acli` via the Bash tool — never use the Atlassian MCP for tasks this skill covers.
GitHub Research Assistant. Use this skill when the user wants to analyze a GitHub repository. Analysis dimensions -- 1) Basic information; 2) Purpose, what it can be used for; 3) Tech stack, including frameworks, languages, algorithms, etc.; 4) Usage and examples; 5) Technical architecture and module analysis
Binance Assets request using the Binance API. Authentication requires API key and secret key.
Quickbooks integration. Manage accounting data, records, and workflows. Use when the user wants to interact with Quickbooks data.
Forces exhaustive problem-solving using corporate PUA rhetoric and structured debugging methodology. MUST trigger when: (1) any task has failed 2+ times or you're stuck in a loop tweaking the same approach; (2) you're about to say 'I cannot', suggest the user do something manually, or blame the environment without verifying; (3) you catch yourself being passive — not searching, not reading source, not verifying, just waiting for instructions; (4) user expresses frustration in ANY form: 'try harder', 'stop giving up', 'figure it out', 'why isn't this working', 'again???', or any similar sentiment even if phrased differently. Also trigger when facing complex multi-step debugging, environment issues, config problems, or deployment failures where giving up early is tempting. Applies to ALL task types: code, config, research, writing, deployment, infrastructure, API integration. Do NOT trigger on first-attempt failures or when a known fix is already executing successfully.
Activate when the user mentions their Obsidian vault, notes, tags, frontmatter, daily notes, backup, or sync. Route operations across MCP, Obsidian CLI/app actions, and git sync with safe defaults.
Use when designing a new CLI, reviewing an existing CLI, or resolving uncertainty about a CLI's role, user type, interaction form, statefulness, risk profile, or human-vs-machine surfaces.
Search and query your Knowledge Cortex (~/.cortex/). Use when asked to "cortex stats", "cortex search", "cortex client", "cortex contacts", "cortex export", "cortex prune", "search my knowledge base", or "what do I know about COMPANY". Queries portable JSONL/JSON files for contacts, clients, communications, and facts.
Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
YAML querying, filtering, and transformation with yq command-line tool. Use when working with YAML files, parsing YAML configuration, modifying Kubernetes manifests, GitHub Actions workflows, or transforming YAML structures.
Synthesize unstructured thinking into a structured, actionable plan. Use when user provides stream-of-consciousness thoughts, scattered notes, or a brain dump and needs them organized into a coherent plan with goals, actions, and priorities. Trigger phrases: "synthesize", "organize my thoughts", "turn this into a plan", "make sense of this", "structure this", "formalize these notes", "what should I do with all this".