Loading...
Loading...
Found 1,123 Skills
Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): "make a PDF", "generate a report", "write a proposal", "create a resume", "beautiful PDF", "professional document", "cover page", "polished PDF", "client-ready document". FILL (complete form fields): "fill in the form", "fill out this PDF", "complete the form fields", "write values into PDF", "what fields does this PDF have". REFORMAT (apply design to an existing doc): "reformat this document", "apply our style", "convert this Markdown/text to PDF", "make this doc look good", "re-style this PDF". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.
High-quality article translation skill, adopting a four-step professional translation workflow: **Analysis → Initial Translation → Review → Final Draft**. Only supports Chinese ↔ English, Chinese ↔ Japanese translation. Triggered when users explicitly request translation using terms such as "翻译", "translate", "精翻", "翻訳", "翻译文章", "translate to Chinese/English/Japanese", "改成中文", "改成英文", "改成日文", "翻成中文", "翻成日文", "翻成英文", "英译中", "中译英", "中译日", "日译中", "日本語に翻訳", "中国語に翻訳", "英語に翻訳", "これを翻訳して", "put this in Chinese", "put this in English", "put this in Japanese", "convert to Chinese", "convert to English", "convert to Japanese", "帮我翻一下", "本地化", "localize", "这篇文章翻译一下", or provide a URL/file/text body and explicitly request a final draft in the target language. Not applicable to requests for only summarization, explanation, comprehension, or organization. If the input is a URL, prioritize using `curl -L` to request `r.jina.ai` to fetch the body content in Markdown; if fetching fails or the content is incomplete, you must stop immediately and ask the user to provide the full text themselves.
Decompose technical design into agent-sized implementation issues → numbered markdown files. Triggers: 'plan this,' 'break into issues,' 'create tasks,' 'ready to implement,' post-architect. Not for: designs without file paths/phases (run architect first).
Automated web QA skill: analyzes a website or project, generates end-user use cases, derives a structured test plan, executes tests via Playwright browser automation, and produces a full HTML/Markdown QA report with screenshots and pass/fail results. TRIGGER this skill whenever the user asks to: test a website, run QA on a web app, check if a site works, find bugs on a site, validate a web project, create a test plan for a website, run functional tests, check a landing page, audit a web app for issues, test user flows — or any variation of "проверить сайт", "протестировать сайт", "QA сайта", "тест веб-приложения", "найти баги на сайте". Even if the user just says "посмотри работает ли всё нормально на сайте" — use this skill.
Interact with Atlassian Jira and Confluence using REST APIs — no MCP server needed. Use this skill whenever the user mentions Jira, Confluence, Atlassian, tickets, issues, sprints, backlogs, epics, stories, or any project management task that involves creating/editing/searching/transitioning Jira issues, writing or reading Confluence pages, generating status reports, triaging bugs, converting specs to backlogs, capturing tasks from meeting notes, searching company knowledge, syncing local BMAD documents with Jira or Confluence, pushing docs to Jira, pulling from Jira, linking documents to tickets, downloading Confluence spaces to local markdown, or converting between Confluence storage format and markdown. Also trigger when the user says things like "move that ticket to done", "what's the status of PROJ-123", "create a bug for X", "search our wiki for Y", "file a ticket", "check for duplicates", "write a status update", "break this spec into stories", "sync this doc", "push to jira", "pull from jira", "sync to confluence", "link this to jira", "sync my epics", "download confluence pages", "sync confluence space", "convert confluence to markdown", or "pull docs from confluence". If there is even a chance the user wants to interact with Jira or Confluence, use this skill.
Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.
Fetch real-time web data via the hasdata CLI. Use when the user wants search results, news, fact-checks, product or seller info, current prices, reviews, real-estate listings or sold comps, vacation rentals, local-business contact details, job postings, salary research, search trends, images, flights, social profiles, or to scrape any URL (HTML / markdown / AI-extracted JSON). Also use when the user asks to summarize a web page, ground a prompt with current information, verify a URL is live or render a JavaScript-heavy page, monitor a price over time, find a phone number or address for a business, build a competitor map, identify recent sold comparables, gather employer reviews, fan out a list of items to per-item details, or check what's being said online about a topic right now. Backed by Google, Bing, Amazon, Shopify, Zillow, Redfin, Airbnb, Yelp, YellowPages, Indeed, Glassdoor, Instagram, Google Maps / Trends / News / Images / Flights / Events APIs.
CRITICAL RULE: You MUST use this skill whenever the task involves any machine learning tasks or data analysis. Use this skill if the user's prompt or requirements mention any of the following: * Clustering * Classification * Regression * Time series forecasting * Statistical testing * Model comparison * ML * Data analysis SQL/BigQuery ML HANDOFF: If the user requires a SQL solution, use this skill to dictate the ANALYSIS STEPS (e.g., markdown analysis cells, visualization logic), but defer to `bigquery` for all SQL syntax.
This skill is to be used when users explicitly request "migrate LaTeX templates", "integrate old projects into ChineseResearchLaTeX", "apply old bids/papers/graduation theses/resumes to the current template", "organize Word/PDF/Markdown/scattered tex files into existing projects", or directly mention `transfer-old-latex-to-new`. The old alias `migrating-latex-templates` is also supported. This skill only migrates the main content to the content layer of the existing templates in the current repository; it must never modify the source code of public packages in `packages/`, nor modify the template styles or entry skeletons in `projects/`, and can only write to content files allowed to carry the main content in the target project.
Add `///` doc strings to public objects in Motoko modules so that `mo-doc` produces useful HTML/Markdown documentation. Covers placement rules, formatting, code examples, common pitfalls, and a verification workflow.
Generate academic presentation-style HTML slide decks and browser reports from PDFs, structured text, Markdown, paper summaries, outlines, or research notes. Use whenever the user wants to convert a scientific paper PDF directly into an interactive HTML report, clickable web presentation, shareable browser deck, or PPT-like HTML output with figures, structured insights, section pages, and offline deck-directory output. In the Aut_Sci_Write suite, choose this skill when the user wants HTML/web output; choose sci-ppt when they explicitly need a .pptx file.
Chat with your agent about projects, recommendations, and canonical papers in Paperzilla. Use when users ask for recent project recommendations, canonical paper details, markdown-based summaries, recommendation feedback, feed export, or Atom feed URLs.