513 件 ・ 関連度順
概要と使いどころ
Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of...
日本語の概要は準備中です。原文の説明を表示しています。
Composes a Discussion around key findings, mechanisms, clinical relevance, and limitations. Use when writing or improving a Discussion section for any biomedical manuscript — including interpreting results, connecting to prior literature, addressing unexpected findings, framing limitations, and writing the conclusion. Also triggers on "write my discussion", "help me discuss my findings", "how do I compare to prior studies", "write the limitations paragraph", or "draft a discussion for my paper".
日本語の概要は準備中です。原文の説明を表示しています。
Acknowledges limitations in sample, design, measurement, and validation in a professional way that improves credibility without undermining the whole paper. Use when writing the limitations paragraph of a Discussion section, preparing a grant risk assessment, responding to reviewers about study weaknesses, or framing scope boundaries for a paper. Also triggers on "write my limitations", "how should I address the limitation of", "reviewer said my sample is too small", or "help me word this limitation".
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
日本語の概要は準備中です。原文の説明を表示しています。
Verify what PR review comments have been addressed (committed/pushed OR uncommitted local changes) and resolve the threads that are genuinely fixed or no longer relevant.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "calculate TAM", "determine SAM", "estimate SOM", "size the market", "calculate market opportunity", "what's the total addressable market", or requests market sizing analysis for a startup or business opportunity.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a structured response-to-referees document from a referee report and the revised manuscript. Maps each referee comment to the specific revision, classifies coverage (addressed / partially / deferred / disagreement), and drafts polite but firm responses. Use during the R&R (revise-and-resubmit) stage of paper revision.
日本語の概要は準備中です。原文の説明を表示しています。
Half-hour television comedy craft (半小时情景喜剧/笑点力学/困境机器/多机位单机位格式) — merged from Evan S. Smith's Writing Television Sitcoms (premise-driven comedy in three levels, nine predicaments, six character mixes, setup/punchline mechanics, toppers, running gags, ten comedic nuances, format rules), Neil Landau's sitcom seven-step formula and comedy-room models, Richard Blum's act-length and set-count parameters, Phoebe Waller-Bridge's Fleabag scripts (direct address as a season-long device, six-episode skeleton), Pamela Douglas on dramedy, Kam Miller on complementary comic traits, and Jesse Armstrong on jokes carrying tragedy. Use when writing or fixing a sitcom episode or spec, raising joke density per page, designing a comic predicament that generates stories, choosing between multi-camera and single-camera format and page counts, structuring cold open/acts/tag, writing a half-hour pilot, running a comedy punch-up, or making a drama funny without shifting genre.
日本語の概要は準備中です。原文の説明を表示しています。
Build and ship Unity 6.3 LTS players: build settings and scenes, player/quality settings, the IL2CPP vs Mono scripting backend, managed code stripping, scripted BuildPipeline.BuildPlayer, and CI/headless builds. Use when configuring or automating a build, choosing a scripting backend, shrinking build size, or when the user mentions Unity build, player settings, IL2CPP, code stripping, or Addressables.
日本語の概要は準備中です。原文の説明を表示しています。
Check whether you're burning out as a caregiver — and get a realistic plan to protect yourself before you can't keep going. Use when asked I'm exhausted from caregiving, am I burning out caring for my parent, caregiver stress help, or I have nothing left to give. Produces an honest read on your burnout signs and how depleted you are, permission and reasons to accept help (which caregivers resist), specific ways to get support and respite, the guilt and identity traps to address, and a realistic self-care plan that fits a caregiver's actual life — because a caregiver who collapses can't care for anyone. Not medical or mental-health treatment.
日本語の概要は準備中です。原文の説明を表示しています。
Build a tiered classroom behavior intervention plan (BIP) for a K-12 student, grounded in the function of the behavior. Use when asked to plan a behavior intervention, address a disruptive or off-task pattern, write a BIP, or set up positive behavior supports. Produces a function hypothesis, prevention/antecedent strategies, teaching of a replacement behavior, a response plan for when it happens, and a simple data-tracking method — positive and skill-building, not punitive.
日本語の概要は準備中です。原文の説明を表示しています。
Scrape Google Maps business listings (name, address, phone, website, rating, reviews, lat/lng, hours, emails) via the local gosom google-maps-scraper REST API. Use when the user wants local-business / lead-gen data, "a list of [businesses] in [place]", or to enrich places with contact info. NOT for Instagram/TikTok/YouTube or any social-media scraping.
日本語の概要は準備中です。原文の説明を表示しています。
Help users identify why a team is struggling and implement a structured recovery plan by addressing leadership gaps, individual performance, and structural misalignments.
日本語の概要は準備中です。原文の説明を表示しています。
Print and mail physical letters and postcards through Lob, verify US addresses, and cancel pieces before production. Trigger phrases: lob, send postcard, send letter, direct mail, print and mail.
日本語の概要は準備中です。原文の説明を表示しています。
Look up registered vehicle owners and residents using the CarsXE Ownership API (Enterprise). Use this when the user asks who owns a VIN, who lives at an address, contact details for a named person, or people in a ZIP. Do not use for lien/theft checks or vehicle history reports.
日本語の概要は準備中です。原文の説明を表示しています。
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
日本語の概要は準備中です。原文の説明を表示しています。
Use when responding to an American Economic Review: Insights (AER: Insights) conditional-accept decision — addressing the editor's letter within the short window, usually without a second referee round. Drafts a concise, decisive response and revision plan; it does not redo the analysis (see aeri-robustness / aeri-identification).
日本語の概要は準備中です。原文の説明を表示しています。
Use when anticipating the objections a sophisticated American Economic Journal: Applied Economics (AEJ: Applied) referee will raise, so a manuscript pre-empts them before submission or addresses them in revision. Plans the defense; it does not draft the response letter (aeja-rebuttal) or run the submission preflight (aeja-submission).
日本語の概要は準備中です。原文の説明を表示しています。
Use when situating an Administrative Science Quarterly (ASQ) manuscript within organization-theory conversations and sharpening the gap/tension it addresses. Positions the argument; it does not develop the core theory or write the methods.
日本語の概要は準備中です。原文の説明を表示しています。
Use when responding to 《会计研究》 (Accounting Research) reviewer reports / an R&R — drafting a point-by-point response letter and 修改说明 that addresses accounting-measure construction, institutional/standard accuracy, identification, and information-mechanism concerns, while keeping the revision anonymous. Use only after the manuscript itself has been revised.
日本語の概要は準備中です。原文の説明を表示しています。
Use when stress-testing the LOGIC of an Academy of Management Review (AMR) theory manuscript — checking logical coherence, running thought experiments and counterfactuals, addressing alternative explanations and disconfirming cases, and verifying each proposition follows from its argument. This is ARGUMENT DEVELOPMENT, NOT data analysis; AMR publishes no datasets, no statistics, and no empirical results.
日本語の概要は準備中です。原文の説明を表示しています。
For churned accounts, research what has changed since they left — new funding, team growth, competitor dissatisfaction, product updates that address their pain — then assess re-engagement potential and generate a personalized win-back email sequence with timing recommendations. Chains web research and LinkedIn monitoring with email sequence generation.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a scored Total Addressable Market (TAM) using Apollo Company Search. Discovers companies matching ICP, scores fit (0-100), assigns tiers (1/2/3), and auto-builds a persona watchlist for Tier 1-2 companies using Apollo People Search (free). Outputs to CSV.
日本語の概要は準備中です。原文の説明を表示しています。