Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.
日本語の概要は準備中です。原文の説明を表示しています。
354 件 ・ 関連度順
概要と使いどころ
Drafts formal explanation letters for Canadian Study Permit applications by structuring the argument around program attractiveness, background relevance, choice rationale, and family benefits.
日本語の概要は準備中です。原文の説明を表示しています。
Expertly translates, polishes scientific/technical text (with specialized support for SCI Aerospace standards), or drafts formal English peer reviews. Ensures accuracy, clarity, and adherence to high academic standards.
日本語の概要は準備中です。原文の説明を表示しています。
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
한국어 블로그·장문 글을 12개 voice preset으로 작성하거나 다듬는다 — toss-tech-design (default), karrot-neighborly, brunch-maker-popular, naver-d2-engineering, biz-formal-report, academic-paper, journalism-broadsheet, kakao-warm-product, line-global-saas, academic-lecture-essay, emotional-brand, legal-disclosure.
日本語の概要は準備中です。原文の説明を表示しています。
Formal theorem proving with research, testing, and verification phases
日本語の概要は準備中です。原文の説明を表示しています。
Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.
日本語の概要は準備中です。原文の説明を表示しています。
Formal evaluation framework for Claude Code sessions implementing eval-driven development (EDD) principles
日本語の概要は準備中です。原文の説明を表示しています。
Run or resume the complete Standard mathematical-modeling workflow from contest files through reproducible evidence, adaptive formal writing, native-equation Word output, and final render QA. Use as the entry point for complete-paper requests.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Give advisory feedback on a plan, design or code change. Use when: asked for an opinion or a look-over, even informally. Not for acceptance; use Validate.
日本語の概要は準備中です。原文の説明を表示しています。
Decision rubric for promoting a prose prompt into a typed DSPy Signature. This is an ENHANCE overlay on top of the [[dspy]] library skill: it does NOT teach DSPy syntax — it answers the coder-agent decision "when do I stop hand-writing a prompt string and declare it as a `dspy.Signature`, and how do I name/describe its fields so the optimizer and the calling code both get a clean contract." Activate when: a prompt string grows past ~50 lines; the LM output is consumed by code (parsed, branched on, stored) rather than read by a human; the same prompt is reused across >1 call site; or a teammate asks "should this be a Signature?". Do NOT activate for one-shot throwaway prompts, or for HOW-TO questions about DSPy modules /optimizers/compile — defer those to the [[dspy]] skill and the [[agentsop-dspy]] workflow skill. Search keywords: typed prompt, structured prompt, DSPy Signature, prompt as a function, prompt contract, when to formalize a prompt.
日本語の概要は準備中です。原文の説明を表示しています。
Automated contract verification, detection, and remediation across multiple languages using formal preconditions, postconditions, and invariants. This skill provides both reference documentation AND execution capabilities for the full PLAN -> CREATE -> VERIFY -> REMEDIATE workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Conducting systematic, scoping, and narrative literature reviews. Covers PRISMA/PRISMA-ScR protocols, search strategy (Boolean, MeSH), database selection (PubMed, Scopus, Web of Science, Embase), screening, data extraction, evidence synthesis (narrative, meta-analysis, thematic), and reporting. Use when planning or executing a formal literature review.
日本語の概要は準備中です。原文の説明を表示しています。
When a founder needs to create a sales proposal, statement of work, contract, NDA, or master service agreement. Activate when the user mentions proposal, SOW, quote, contract, NDA, MSA, or needs to formalize a deal.
日本語の概要は準備中です。原文の説明を表示しています。
Searches academic literature via arXiv, Semantic Scholar, and open-access PDFs. Use when building literature reviews or finding formal research on a topic.
日本語の概要は準備中です。原文の説明を表示しています。
Generates monthly/quarterly investor updates. Takes KPIs, milestones, challenges, financials. Writes professional investor-update.md with highlights, metrics dashboard, product updates, team news, financial summary, upcoming milestones, asks. Multiple tones from seed-stage casual to Series B formal. Use when founders need to communicate progress to investors.
日本語の概要は準備中です。原文の説明を表示しています。
Guides preparation for supervisory authority (DPA) inspections and investigations including document readiness checklists, interview preparation for key personnel, technical demonstration procedures, on-site logistics, response protocols, and post-inspection follow-up. Covers unannounced inspections, formal audits, and complaint-triggered investigations. Keywords: DPA inspection, supervisory authority, investigation, readiness, interview preparation, response protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Create original short videos using the 边界执行|正式基线—干扰定位—处置—复位 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Create, polish, and quality-check editable undergraduate or graduate thesis defense PowerPoint decks from a local thesis PDF/LaTeX project and an existing PPTX template. Use when the user asks for a formal defense PPT, thesis presentation, academic答辩PPT, template-matched PPTX, or local PowerPoint deck generation with visual inspection.
日本語の概要は準備中です。原文の説明を表示しています。
Use Jacobian's MCP operations for nontrivial mathematical computation, finite search, structural analysis, formal checking, probability, or optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Use BIRD Book Deconstructor 2.2 to apply the formal BIRD 2.1 Knowledge Address protocol to complex manuscript text and TheBrain Thoughts. Use when splitting books into chapter/section/item knowledge nodes, assigning Book Address, structured Knowledge Index (Weight, Type, Keyword, Alias), Routes, verified Deep Links, and Semantic Roles; producing BIRD Excel workbooks, TheBrain scaffolds, Roam JSON, monochrome printable double nine-grid cards, or a routed handoff from iMandalArt to A4 eight-page booklets; or auditing and migrating existing BIRD/TheBrain indexes.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically simplify and minimize TLA+ specifications by reducing redundant state variables, merging equivalent actions, and minimizing invariants while preserving specified properties. Use when working with TLA+ specifications that need optimization, simplification, or reduction. Triggers when users ask to minimize, reduce, simplify, or optimize TLA+ specs, or when they want to remove redundancy from formal specifications while maintaining semantic equivalence.
日本語の概要は準備中です。原文の説明を表示しています。
Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks. Use when you need to debug complex issues, reproduce test cases, prepare traces for formal verification, or analyze program execution. Supports manual instrumentation points, automatic function/method instrumentation, and conditional triggers. Outputs structured JSON snapshots for debugging, replay, and verification workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Extract language-agnostic pseudocode from formally verified programs (Isabelle/HOL, Coq) while preserving verified control flow, data dependencies, and algorithmic logic. Use when: (1) Users have verified code and need readable pseudocode, (2) Documenting verified algorithms for broader audiences, (3) Translating verified implementations to other languages, (4) Creating algorithm specifications from verified code, (5) Preserving verification guarantees in pseudocode form, or (6) Abstracting proof-heavy code to essential logic. Maintains semantic faithfulness to verified implementation.
日本語の概要は準備中です。原文の説明を表示しています。