Loading...
Loading...
Found 111 Skills
Advanced RAG with Self-RAG, Corrective-RAG, and knowledge graphs. Use when building agentic RAG pipelines, adaptive retrieval, or query rewriting.
Use when designing or rewriting a high-converting SaaS pricing page (structure, plan design, copywriting, SEO/AEO, FAQs, layout patterns, experiments). Includes checklists, templates, and common pitfalls.
Enable efficient communication between Thai-language users and agents by translating Thai prompts into English in two modes and by preventing Thai text corruption in files. Use when the user writes in Thai, asks for Thai-to-English interpretation, wants token-efficient prompt rewriting, or reports mojibake/replacement-character issues such as U+FFFD in saved files.
Color-code the Obsidian graph view by rewriting `.obsidian/graph.json` colorGroups. Use this skill when the user says "color my graph", "color code obsidian", "colorize the graph", "color the graph by tag", "color by category", "highlight visibility in graph", "make the graph colorful", "distinguish tags in graph", or wants nodes in Obsidian's graph view tinted by tag, folder, or visibility. Generates a `colorGroups` array from the vault's actual tags/categories and merges it into the existing graph.json without clobbering other graph settings. Always backs up first.
Revise general Chinese, mainland Chinese legal terms, or legal text with AI writing traces into a natural, precise professional style that conforms to the legal practice of the Republic of China (Taiwan). This skill must be used when users mention legal term conversion, pleading polishing, contract text adjustment, removing AI traces from legal opinions, Taiwan legal tone, certified letters, or legal document revision; no new legal claims, legal sources, or changes to rights and obligations shall be added through rewriting.
You MUST use this when drafting, rewriting, shortening, tightening, reviewing, or explaining edits to prose in English or Ukrainian for a particular reader - docs, READMEs, PR descriptions and review replies, chat messages, emails, articles, reports, and product copy - including a single paragraph, email, or reply the user pastes, requests to make text clearer, shorter, less generic, less AI-sounding, or less bureaucratic, and rewriting a draft to match a sample of the author's writing. Dash policy belongs to dashfix, negative-parallelism audits to negafix, deciding whether a review finding is valid to review-resolution, agent instruction files to maintaining-agent-context, and interface copy written while designing a UI to frontend-crafting. Not for translation.
Extract Feishu (Lark) Docs, Wiki pages, Wiki collections/hubs, spreadsheets, and Minutes (妙记) transcripts into clean high-fidelity local Markdown. The primary path is the lark-cli API — programmatic extraction with no LLM rewriting of the body — which recursively follows a collection's reference graph (mention-doc / sheet / cross-tenant links) and uses error codes to resolve permission boundaries precisely; a browser-DOM path is the fallback only when lark-cli cannot reach the content. Use this whenever the source is a Feishu/Lark URL and fidelity matters — including 导出飞书文档/合集/妙记转写, 把飞书 wiki/知识库转 markdown, scraping or archiving a Feishu collection, exporting a Feishu Minutes/妙记 transcript, or saving a Feishu page locally — even if the user only says clipping, archiving, converting, or "save this". Also covers the permission-denied path (owner-exported .docx → faithful Markdown with heading/highlight restoration).
Creates isolated container environments for testing local uncommitted changes before pushing. Use when testing library changes, multi-repo coordination, or validating "works on my machine" → "works in CI". Provides git bundle snapshots, embedded git server, selective URL rewriting, and package manager cache isolation. Works with any coding agent via standalone CLI, shell scripts, or Docker Compose.
Use when writing, rewriting, or reviewing PR/CL descriptions, commit messages, or code-change summaries that explain what changed and why. TRIGGER on "write PR description", "improve this commit message", "summarize this diff", "CL description", "change description", or "make this PR/CL description easier to review". DO NOT TRIGGER for code review, PR splitting, code restructuring, user-facing changelogs, or reviewer replies unless the requested output is a change description.
Own assessment-only manuscript deliverables without rewriting: full scientific review, scoring, reviewer reports, issue diagnosis, AC/meta-review, readiness judgment, writing/format review, and cross-version comparison. Use for full review, scientific review, do not rewrite, assessment-only, paper review, score drift, moving-target review, 完整审稿, 不要改写, 模拟审稿, 论文评分, 版本对比, 复审一致性, 写作评审, LaTeX检查. Requests for revised or polished prose, including rewrite based on reviews with no new review, belong to ccf-paper-writer; rebuttals belong to ccf-rebuttal-writer; visual/table styling belongs to ccf-visual-composer.
Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.
ast-grep rule writing and usage best practices. This skill should be used when writing, reviewing, or debugging ast-grep rules for code search, linting, and transformation. Triggers on tasks involving YAML rules, pattern syntax, meta variables, constraints, or code rewriting.