Loading...
Loading...
Found 6,273 Skills
Skill for optimizing article style to remove AI flavor. Used to identify and rewrite issues such as AI traces, template tone, material-like style, translationese, empty buzzwords, excessive golden sentences, overuse of em dashes, bullet stacking, and random bolding in articles, official account drafts, self-media drafts, oral broadcast scripts, speech scripts, course scripts, and product copy; activated when users say phrases like "remove AI flavor", "eliminate AI traces", "not written by AI", "more human-written", "more natural", "less robotic", "remove template feel", "polish to official account final draft". Not applicable for fact-checking, zero-based topic planning, converting papers to official account articles, pure title generation, or pursuing AI detector pass rates.
Use when the user wants to create or update a DDD-style ubiquitous language glossary, define domain terms, resolve ambiguous terminology, harden naming, or write UBIQUITOUS_LANGUAGE.md from the current conversation and codebase context.
[Hyper] Create and refactor AI-readable docs, instruction bases, runbooks, specs, and harness-ready rule packs for context, prompt, tool, eval, sourcing, safety, and validation workflows.
[Hyper] Use when working on Vite + TanStack Router projects - enforces architecture rules (layers, routes, hooks, services, conventions) with mandatory validation before any code change. Triggers on file creation, route work, hook patterns, or any structural change in a Vite + TanStack Router codebase.
Fills gaps in existing healthcare practitioner lists — adds missing phone numbers, credentials, specialties, contact info, education, reviews, and regulatory data. Triggers: "enrich my provider list", "fill in missing data", "add phone numbers to these doctors", "complete this practitioner database", "enrich CRM export", "fill gaps in my provider data", "supplement this healthcare list". Accepts CSV, Google Sheet URL, or pasted data. Searches for each provider's practice website, extracts missing fields, and enriches with reviews, clinical trials, and accreditation via WSAs. Do NOT use for extracting providers from practice URLs — use healthcare-providers-extract instead. Do NOT use for validating credentials — use healthcare-providers-verify instead. Do NOT use for discovering practices — use market-finder or local-places instead. Do NOT use for general extraction — use nimble-web-expert instead.
Scaffolds Remotion project folder structure, base configuration files, and file organization. Focuses ONLY on directory creation, empty file templates, and Remotion configuration. Use when starting a new video project or when asked to "scaffold Remotion project", "create project structure", "setup Remotion folders".
Must be used when users explicitly request "recommend submission journals", "help me choose SCI journals for my paper", "which journals is this manuscript suitable for", "journal matching/journal selection/submission suggestions". Applicable to scenarios where users provide full text, abstracts, Markdown, LaTeX, PDF, Word, or mixed materials; This skill will first use the built-in `2023IF.xlsx` to perform minimum hard filtering to generate a candidate pool based on the manuscript and user preferences, then the host model will independently plan Set1/Set2/Set3, verify the scope / quality / PubMed papers of the last 3 months via the internet, and finally output a Markdown journal selection report sorted by recommendation level. ⚠️ Not applicable: Users only want to polish papers, only want to translate abstracts, or only ask about the official website information of a single journal without needing systematic journal selection.
This skill is used when users explicitly request "LaTeX template optimization", "style parameter alignment", "pixel-level comparison", "make-latex-model" or the old notation "make_latex_model", or when they want to turn a project in ChineseResearchLaTeX into a high-quality template. It supports four product lines: NSFC / paper / thesis / cv; first determine whether to modify the project layer or the public package based on the actual hierarchy of packages/ and projects/, then use the official build entry of each product line for acceptance. If modification to the public packages under packages/ is necessary, a regression plan for affected templates must be generated first and relevant regression completed; the NSFC special tool is only used on demand when it clearly falls into the NSFC parameter alignment scenario.
Store and query vector embeddings using Amazon S3 Vectors, a cost-effective long-term vector storage service with its own API namespace (s3vectors). Triggers on: create S3 vector bucket, vector index, store embeddings, semantic search, RAG vector storage, similarity search, vector database, migrate from other vector databases. Do NOT use for: querying tabular data (use querying-data-lake), S3 object storage, or hundreds/thousands of sustained QPS (use OpenSearch).
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the top of "我的设计". Each connector module picks its own UI form (list, avatar stack, status ring, heatmap, file grid, alert card, …) based on the data shape it returns, so the layout scales as Orbit's connector ecosystem grows. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against the user's live connector data.
Run a full Flows app platform review against a React/TypeScript CDF codebase, following the cognitedata/dune-app-reviews scoring criteria. Produces three artifacts: review-files.md (per-file inventory), review-packages.md (dependency audit), and review-report.md (scored report with must/should/nice-fix items). Use when the user asks for a Flows app review, pre-submit review, approval review, app certification review, code quality audit, CDF platform review, or "run dune-review" on a codebase before submission.
Compare a paper's claims against its public codebase. Use when the user asks to audit a paper, check code-claim consistency, verify reproducibility of a specific paper, or find mismatches between a paper and its implementation.