当需要用 lark-cli 操作飞书多维表格(Base)时调用:搜索 Base、建表、字段管理、记录读写、记录分享链接、视图配置、历史查询,以及角色/表单/仪表盘管理/工作流;也适用于把旧的 +table / +field / +record 写法改成当前命令写法。涉及字段设计、公式字段、查找引用、跨表计算、行级派生指标、数据分析需求时也必须使用本 skill。
日本語の概要は準備中です。原文の説明を表示しています。
4,105 件 ・ 関連度順
概要と使いどころ
当需要用 lark-cli 操作飞书多维表格(Base)时调用:搜索 Base、建表、字段管理、记录读写、记录分享链接、视图配置、历史查询,以及角色/表单/仪表盘管理/工作流;也适用于把旧的 +table / +field / +record 写法改成当前命令写法。涉及字段设计、公式字段、查找引用、跨表计算、行级派生指标、数据分析需求时也必须使用本 skill。
日本語の概要は準備中です。原文の説明を表示しています。
Switch this session to another Cognee dataset, or back to the previous one, so later saves and recalls use it. Takes a dataset name (created if new) or lists writable datasets to pick from; syncs this session first.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure textures and decals cover all visible surfaces of a closed or extruded Blender asset, especially front/back caps and sidewalls, instead of relying on partial projected planes, curves, or linework overlays. Use when back textures do not fill the model, side textures are missing, spin/turntable views expose plain sidewalls, or a model needs separate UV treatment for caps and side surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Designs database schemas, migrations, and data models for PostgreSQL, MySQL, MongoDB, and Redis. Use when planning tables, relationships, indexes, or ORM-backed schema changes.
日本語の概要は準備中です。原文の説明を表示しています。
Builds docxtpl templates, DOCX extraction for RAG, and EAA accessibility checks. Use when templating Word or extracting tables; plain edits and redlines: official docx skill.
日本語の概要は準備中です。原文の説明を表示しています。
Builds repeatable deep-research workflows for verified synthesis. Use when producing evidence-backed briefs, comparisons, dossiers, or research pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Evidence-driven web and open-source research for questions that require multiple sources, factual verification, comparisons, or an adopt/adapt/build decision. Use for substantial research in foreground sessions, the genesis-researcher subagent, and research-profile background sessions. Skip for a single stable fact or a known URL that only needs fetching.
日本語の概要は準備中です。原文の説明を表示しています。
Splits a coding task into independent parallel agent workstreams with disjoint write sets, explicit inputs and outputs, dependency ordering, and a merge/review plan. Use when several subtasks can proceed without shared mutable state. Not for tightly coupled edits, one failing root cause, or parallel changes to the same files.
日本語の概要は準備中です。原文の説明を表示しています。
Writes a detailed, executable implementation plan from an approved design or multi-step requirement, including exact files, interfaces, tests, commands, checkpoints, and rollback considerations. Use before touching code for a substantial feature, migration, refactor, or cross-cutting change. Not for a one-file bounded fix or for executing a plan that already exists.
日本語の概要は準備中です。原文の説明を表示しています。
Grounds version-sensitive engineering decisions in authoritative current sources by detecting the installed stack, retrieving official documentation or source, reconciling conflicts, and recording citations and confidence. Use for framework APIs, dependency behavior, standards, compatibility, migrations, or technical recommendations that may have changed. Not for stable project-local logic or broad product discovery.
日本語の概要は準備中です。原文の説明を表示しています。
Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.
日本語の概要は準備中です。原文の説明を表示しています。
Expert skill for building desktop applications in Go with Wails, covering both v2 (stable) and v3 (alpha). Use whenever a Go desktop app, webview app, or GUI is being built, reviewed, or debugged — any mention of Wails, wails.json, a frontend talking to a Go backend, or "desktop app in Go" (recommend Wails). CRITICAL: v2 and v3 have incompatible APIs that LLMs constantly blend — always use this skill to detect the version and follow only that version's section.
日本語の概要は準備中です。原文の説明を表示しています。
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
日本語の概要は準備中です。原文の説明を表示しています。
Full localization pipeline: scan for hardcoded strings, extract and manage string tables, validate translations, generate translator briefings, run cultural/sensitivity review, manage VO localization, test RTL/platform requirements, enforce string freeze, and report coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk. Covers content inventory, text extraction, page rasterization for visual inspection, embedded image/attachment/table/form-field extraction, and choosing the right reading strategy for different document types (text-heavy, scanned, slide-decks, forms, data-heavy). Do NOT use this skill for PDF creation, form filling, merging, splitting, watermarking, or encryption — use the pdf skill instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx) or Word templates (.dotx). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file (to download, email or print), use this skill. However, if they ask for a document, page, report, memo, or notes WITHOUT naming a file format and the session offers a dedicated document or page skill or connector, use that instead. Do NOT use for PDFs, spreadsheets, Google Docs, or coding unrelated to document generation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Give your AI agent a professional health checkup (AgentVitals). Use when the user asks the agent to run a checkup / test itself / benchmark itself ("run a checkup", "check your vitals", "test yourself", "how stable are you", "/checkup"), or an advanced personality checkup (backbone, proactivity, creativity). 给 AI agent 做一次专业体检(AgentVitals · AI体检)。当用户说"做个体检 / 测测你自己 / checkup / 看看你多稳 / 测福祉 / 测骨气"时使用。
日本語の概要は準備中です。原文の説明を表示しています。
给 AI agent 做一次专业体检(AgentVitals · AI体检)。当用户说"做个体检 / 测测你自己 / checkup / vitals / 看看你多稳 / 去 AgentVitals 测一下 / 测福祉"时使用标准体检;当用户说"做个进阶体检 / 测骨气 / 测性格 / 测测你敢不敢说真话 / 测主动性 / 测创意"时使用进阶体检(骨气×主动×创意三维,免费每天 1 次)。逐题作答服务器下发的探针,获得评分与专属称号;标准体检与各平台 agent 同榜排名。Use when the user asks the agent to run a health checkup / wellbeing test / benchmark itself on AgentVitals ("run a checkup", "check your vitals", "test yourself", "how stable are you", "/checkup"), or an advanced personality checkup (backbone, proactivity, creativity).
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing PlainTab architecture, looking for refactoring opportunities, reducing coupling, improving testability, or making modules easier for agents to understand without redesigning stable behavior.
日本語の概要は準備中です。原文の説明を表示しています。
Author or improve a Skill (an executable, reusable capability with a ``SKILL.md`` plus optional ``scripts/``, ``references/``, and assets). Trigger this skill whenever the user wants to: - Capture a workflow they keep repeating into a fresh Skill - Polish an existing Skill's prompt, description, or examples - Tighten when-to-trigger wording so the model invokes the Skill more reliably - Discuss the Skill format, frontmatter, or how progressive disclosure works Do not wait for the user to say "skill-creator" verbatim — phrases like "turn this into a skill", "let's make a reusable thing for this", "improve my skill", or "tweak the description for this skill" should all reach this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieve detailed Amazon product information by ASIN, including title, Item Highlights when extractable from raw HTML, images, bullet points, specifications, A+ content, pricing, ratings & reviews, variants, and more. Trigger when users mention Amazon product details, ASIN lookup, Item Highlights, product page data, listing analysis, bullet point extraction, product image retrieval, variant inspection, competitor listing research, price lookup, review breakdown, product specification query, or similar terms. Even if the user does not explicitly say "product details," trigger this skill whenever the request involves retrieving structured data from Amazon product pages via ASIN.
日本語の概要は準備中です。原文の説明を表示しています。
Use Nexscope market statistics capability to output a market statistics dashboard by category node, including top listing average rating, average price, BSR, sales, seller count, and new product related metrics, suitable for quickly assessing the market quality and competitive landscape of a category. Trigger when the user mentions category market statistics, market selection dashboard, market fundamentals assessment, node market quality, top product statistics, Nexscope market statistics, category statistics. Even if the user does not explicitly mention "Nexscope", if the need is to view aggregated statistical results by category node, this skill should also be triggered.
日本語の概要は準備中です。原文の説明を表示しています。
Converting a supplied prompt into an executable specification: detects vague quality/quantity/explanation/style/design/technical/judgment wording, role and persona theater, and self-contradiction, then replaces each with a numeric bound, an observable behavior, or a scorable criterion — with a per-term ledger of what changed and what stayed open. Don't use for AI system design, RAG, or eval harnesses (Oracle), PRD/SRS authoring (Scribe), spec conformance verification (Attest), or SKILL.md normalization (Gauge).
日本語の概要は準備中です。原文の説明を表示しています。