1,145 件 ・ 関連度順
概要と使いどころ
Explain analysis methodology to diverse audiences. Use when documenting 'how we did this' sections, building trust through transparency, or teaching analytical approaches to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
创建包含 section、problem、solution 和 explainer 的练习目录结构，且能通过 lint 检查。当用户想要搭建练习框架、创建练习模板或设置新的课程章节时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Post-process LaTeX project prose to improve readability through varied sentence and paragraph lengths. Removes filler phrases and unnecessary transitions while preserving all citations and semantic meaning. Use after drafting is complete, when sections read as monotonous or blocky.
日本語の概要は準備中です。原文の説明を表示しています。
Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in the browser instead of editing Markdown. Use when a brief or draft needs to go to a client/expert for review, or when building the briefs/index.html entry page for a client folder. The reviewer's input comes back as a JSON file that 04-content-brief Step 9 ingests. Visual quality is delegated to the frontend-design skill.
日本語の概要は準備中です。原文の説明を表示しています。
Repair a repeatedly failing Standard paper section from repair_queue.json, or generate an explicitly requested legacy/quickstart scaffold. Do not use it as the formal paper writer.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded section template and producing INVENTORY-SKILLS-JAVA.md. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @003-skills-inventory; Inventory Java cursor rule skills; List available Java system prompt skills. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for requests such as Create DEVELOPER.md; Generate DEVELOPER.md; Maven project documentation; Add Maven documentation; Plugin goals reference. Part of Plinth Toolkit
日本語の概要は準備中です。原文の説明を表示しています。
Neutral, framework-agnostic decision tree for project kickoff: "which agent / RAG / LLM framework should I reach for?" Synthesizes the ecosystem sections of 7 landmark-project SOPs (LangGraph, LlamaIndex, DSPy, CrewAI, vLLM, Aider, Dify) into one layered rubric. Core stance: frameworks are LAYERS, not competitors — a real project usually combines DSPy (compile) + LlamaIndex (retrieve) + LangGraph (orchestrate) + vLLM (serve), and you choose ONE per layer, not one to rule all. Use when starting any LLM/agent/RAG project, or whenever the "which framework?" question is asked. Deliberately neutral — unlike vendor docs and the LangChain-biased `framework-selection` on skill.sh, this skill has no horse in the race.
日本語の概要は準備中です。原文の説明を表示しています。
Trigger for: writing, revising, converting, or descoping a federal Statement of Work, Performance Work Statement, SOW, PWS, or SOO; develop executable requirements; define contract scope; create measurable performance standards; or prepare requirements before an IGCE. Produce a contract-file-ready .docx plus separate chat-only staffing and Section B handoffs. Never place FTEs, SOC codes, staffing estimates, IGCE content, CLINs, or pricing schedules inside the SOW/PWS body. Do NOT use for the IGCE, market research report, acquisition plan, QASP, or clause-selection matrix.
日本語の概要は準備中です。原文の説明を表示しています。
Audit every CLAUDE.md in this project for drift against the last week of git history. Flags sections that reference deleted files, renamed paths, or removed dependencies. Read-only — returns a punch list, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Re-detect this project's tech stack from package.json / requirements.txt / pyproject.toml / go.mod / Cargo.toml and diff it against the Tech Stack section of every CLAUDE.md. Read-only — returns added / removed / renamed dependencies, never edits.
日本語の概要は準備中です。原文の説明を表示しています。
Review the symbol-notation section of a mathematical-modeling paper against the full paper. Check table coverage, symbol meanings, units, overloading, case and subscript consistency, first-use definitions, formula usage, and visible table formatting. Use for symbol-table diagnosis, not general paper review.
日本語の概要は準備中です。原文の説明を表示しています。
Review a mathematical-modeling paper's model-assumption section against the complete problem statement. Diagnose whether each assumption is necessary, evidence-based, compatible with the task, appropriately simplified, and usable by the later model. Use for assumption review, not automatic full-paper review or unsupported assumption generation.
日本語の概要は準備中です。原文の説明を表示しています。
Review a Chinese mathematical-modeling problem-analysis section against the original problem, checking task classification, data reasoning, cross-problem linkage, model-choice rationale, validation planning, chapter boundaries, and the overall solution framework. Use for diagnosis, not automatic full rewriting.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate the BZD mathematical-modeling Skills across problem reading, idea generation, model selection, paper drafting, section checks, final format/AIGC audits and judge-style scoring. Use when a user wants one entry point, an end-to-end competition workflow, the next appropriate Skill, or coordinated processing of a problem and paper.
日本語の概要は準備中です。原文の説明を表示しています。
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
日本語の概要は準備中です。原文の説明を表示しています。
Cargo.toml dependency management patterns for HASH workspace. Use when adding dependencies, managing workspace dependencies, organizing Cargo.toml sections, setting version pinning, configuring default features, or working with public dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
日本語の概要は準備中です。原文の説明を表示しています。
Use for social science academic paper drafting, outlining, diagnosis, review, and revision. Trigger for topic diagnosis, research question refinement, literature review planning, CNKI/Google Scholar literature search-to-Zotero workflows, structured paper reading notes, theoretical framework design, research design critique, draft review, section or paragraph revision, citation and evidence risk checking, causal-claim checking, and pre-submission review. Do not use for purely creative writing or non-academic editing.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain Core UI with the ReUI registry and authenticated ReUI MCP. Use for new pages/sections/features, ReUI components/examples/Pro blocks, @reui installs, REUI_LICENSE_KEY setup, and ReUI API or documentation research. Preserve exact base-maia/Base UI, packages/ui ownership, existing shared tables, and Core tokens; use live APIs and worked examples.
日本語の概要は準備中です。原文の説明を表示しています。
Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
日本語の概要は準備中です。原文の説明を表示しています。
Draft Project Manual specification requirements for EPD submittals and sourced GWP limits. Use for embodied-carbon requirements in project sections; use the EPD parsing, research or comparison skills for product evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Assemble an ordered FF&E specification book from selected product cut sheets, with every product accounted for and verified package receipts. Use for grouped sheets or a combined FF&E book; use spec-writer for Project Manual sections.
日本語の概要は準備中です。原文の説明を表示しています。
Structured peer review of manuscripts and grants. 7-stage evaluation: initial assessment, section review, statistical rigor, reproducibility, figure integrity, ethics, writing. Covers CONSORT/STROBE/PRISMA and report structure. For evidence quality see scientific-critical-thinking; scoring see scholar-evaluation.
日本語の概要は準備中です。原文の説明を表示しています。