「how to use」の検索結果

Compare childcare options — nursery/daycare, childminder, nanny, family, or a mix — for your family's real needs, budget, and values. Use when asked to compare childcare options, nursery vs nanny, how to choose childcare, or find the right childcare. Produces a needs-and-values profile, a side-by-side of the realistic options on cost/flexibility/socialization/control, the questions to ask and red flags to check on visits, a total-cost read (including subsidies), and a decision that fits your priorities — not a generic ranking.

日本語の概要は準備中です。原文の説明を表示しています。

Wrap up a client project the right way — a clean handoff, a strong final impression, and the moves that turn a finished project into referrals and repeat work. Use when asked to wrap up a client project, offboard a client, end a client relationship well, or project handoff. Produces a closeout checklist (deliverables, access, final invoice, documentation), a handoff/wrap-up message, the referral/testimonial/repeat-work asks to make at the peak moment, a graceful process for ending an ongoing relationship, and how to leave the door open — so the ending builds your business instead of just stopping.

日本語の概要は準備中です。原文の説明を表示しています。

Work out whether you're eligible for a class-action settlement or refund program — and actually file the claim before the deadline. Use when asked am I owed money from a settlement, is there a class action for [product/company], how do I claim a settlement, or did I qualify for that refund. Produces a way to check for relevant settlements, an eligibility read against the class definition, the proof you need and how to file, deadline tracking, and honest expectations on payout size — plus how to avoid fake-settlement scams. Not legal advice.

日本語の概要は準備中です。原文の説明を表示しています。

Organize the people and information involved in caring for someone — family, doctors, helpers — so care doesn't fall through the cracks or all land on one person. Use when asked help me coordinate care for, organize caregiving for my parent, set up a care system, or I'm drowning coordinating everyone. Produces a map of who does what (medical, daily, financial, emotional), a shared-information system so everyone's on the same page, a way to divide tasks fairly among family, a communication rhythm, and how to keep the key information (meds, contacts, wishes) in one accessible place — turning caregiving chaos into a coordinated effort.

日本語の概要は準備中です。原文の説明を表示しています。

Work out which applicant tracking system a job uses from its application link, and give the formatting rules that system parses safely. Use when asked which ATS does this company use, will my CV get through the ATS, is my CV ATS friendly, or how should I format for Workday, Greenhouse, Lever or Taleo. Produces the detected system with the evidence, a parsing-safe formatting checklist, the file type to upload, and a check of a supplied CV against the rules.

日本語の概要は準備中です。原文の説明を表示しています。

Draft the hard personal message you keep putting off — chasing money a friend owes, backing out of plans, checking in after a fight, following up on an unanswered text. Use when asked to help send an awkward text, how to say something uncomfortable to a friend, word a difficult personal message, or bring up something touchy. Produces a couple of calibrated options, the one line to open with, and the send/wait/call judgement call — warm, honest, and not a doormat.

日本語の概要は準備中です。原文の説明を表示しています。

Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan.

日本語の概要は準備中です。原文の説明を表示しています。

Build the context an AI needs to do a task well — the background, constraints, examples, and format it can't guess — so you get a great result on the first try instead of a generic one you have to keep correcting. Use when asked why does AI give me generic answers, how do I give AI better context, my AI results are mediocre, or how do I get it right the first time. Produces the specific context this task needs (who/what/constraints/examples/format), a reusable primer you can paste ahead of the request, the difference between a starved prompt and a well-briefed one, and what to leave out — turning vague back-and-forth into a strong first result.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate performance fairly when output is AI-assisted — what still measures the human, what now measures the tooling, and how to run the review conversation. Use when reviewing someone whose work is heavily AI-assisted, when output volume stopped meaning anything, when calibrating a team with uneven AI adoption, or when writing review criteria for the AI era. Produces review guidance: a what-measures-whom analysis, rewritten criteria, calibration rules for mixed-adoption teams, and conversation scripts. For the general review document use performance-review; for redesigning the role itself use role-redesign-for-ai.

日本語の概要は準備中です。原文の説明を表示しています。

ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Each writer exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of written file paths. Use when adding platform support for a new agent, integrating a new code AI tool, or extending caliber to support new targets. Do NOT use for modifying existing writers, refactoring scoring logic, or changing how writers are invoked.

日本語の概要は準備中です。原文の説明を表示しています。

Use when you need to understand how Accounting, Organizations and Society (AOS) evaluates a manuscript — triage by the joint Editors-in-Chief, double-anonymized review by interdisciplinary referees, the meaning of each decision type, and how to read the editor's letter. Explains the process; it does not draft the revision response (aos-rebuttal).

日本語の概要は準備中です。原文の説明を表示しています。

Extract and normalize pricing tiers from any SaaS, API, cloud, or LLM vendor's pricing page. Use this skill whenever the user says "pricing for X", "how much does X cost", "pricing tiers", "cost comparison", provides a URL ending in `/pricing` or `/plans`, or asks to monitor pricing over time. Pairs well with `exportSkill` to turn a run into a cron-friendly workflow. Scrape-driven; no interact needed for typical pricing pages.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user asks to summarize, or asks why Simulink Coverage objectives are missing, unsatisfied, or uncovered on a coverage result they already have — why specific decision, condition, MCDC, relational-boundary, or saturation/overflow outcomes weren't exercised, whether uncovered logic is dead code, or how to close the gap (a test, a coverage filter, or a design change). It reads an existing cvdata, .cvt file, sim-with-coverage output, or Simulink Test result; it never runs cvsim to collect coverage.

日本語の概要は準備中です。原文の説明を表示しています。

Decides whether and how to polish a draft genome assembly to raise consensus accuracy (QV) with read-type-matched tools - Racon and medaka (ONT consensus), dorado polish, Polypolish and pypolca (Illumina, repeat-aware), Pilon (legacy short-read), NextPolish/NextPolish2, Hapo-G (haplotype-aware), ntEdit, and DeepPolisher/PEPPER-Margin-DeepVariant for human. Covers the do-not-polish-HiFi rule, the medaka basecaller-model footgun, held-out Merqury QV as the only honest stop signal, and the haplotype-collapse trap. Use when correcting homopolymer indels or residual SNPs in a long-read assembly, deciding if a HiFi assembly needs polishing, or choosing an ONT vs hybrid vs short-read polishing chain.

日本語の概要は準備中です。原文の説明を表示しています。

Assigns GO terms, Pfam/InterPro domains, KEGG orthologs, EC numbers, and product names to predicted proteins using eggNOG-mapper (orthology), InterProScan (domain signatures), and KofamScan (KEGG), routing specialized functions to dbCAN/antiSMASH/AMRFinderPlus/SignalP. Covers the orthology-vs-domain-vs-homology paradigms, the annotation-error percolation cascade, domain-presence-is-not-function, GO IEA circularity in enrichment, evidence tiering, and bit-score/coverage thresholds. Use when adding functional annotation to predicted genes, choosing between eggNOG-mapper and InterProScan, or judging how much to trust a functional label.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes species-environment relationships with constrained ordination (CCA, RDA, db-RDA), variance partitioning, indicator species (indicspecies IndVal.g group-equalized), PERMANOVA paired MANDATORILY with PERMDISP (Anderson & Walsh 2013; dispersion confounds centroid tests), Joint Species Distribution Models (HMSC, sjSDM, gjam) with explicit rejection of "residual covariance equals biotic interaction", phylogenetic community ecology (SES_MPD/MNTD), trait-environment via RLQ + fourth-corner with corrected modeltype=6 (Dray 2014), bipartite network metrics (NODF, modularity) with curveball null (Strona 2014), and Mantel-test replacements (dbRDA, GDM) for spatial data. Use when testing how environmental gradients structure communities, identifying habitat indicator taxa, partitioning variance among predictors, deciding whether PERMANOVA significance is location vs dispersion, picking among HMSC/sjSDM/gjam, or replacing Mantel tests for landscape data.

日本語の概要は準備中です。原文の説明を表示しています。

Creates sashimi-style plots showing RNA-seq read coverage and splice junction counts using ggsashimi (general-purpose, condition-grouped overlays), rmats2sashimiplot (rMATS-output-aware), MAJIQ-VOILA (LSV posteriors interactive HTML), leafviz (leafcutter clusters Shiny), Jutils (tool-agnostic heatmaps and sashimi for rMATS/leafcutter/MntJULiP/MAJIQ output), or pyGenomeTracks (multi-track publication figures). Tool choice depends on the upstream differential-splicing tool's output format and the publication vs interactive use case. Use when visualizing specific splicing events, validating differential splicing calls, or producing publication-quality figures.

日本語の概要は準備中です。原文の説明を表示しています。

Analyzes code files and reports statistics including line counts, file counts by extension, and total size. Use this skill whenever the user wants to understand the composition of a codebase - asking about "how many lines of code", "what file types exist", "code distribution", or needing a quick audit of project size and structure. Make sure to invoke this skill when users mention analyzing codebases, counting lines, checking file distributions, or auditing code.

日本語の概要は準備中です。原文の説明を表示しています。

TikTok Shop content creation strategy and planning. Trending formats, viral hooks, product showcasing, hashtag strategy, and content calendar development. Use when the user asks about TikTok content strategy, viral content creation, TikTok marketing, or content planning.

日本語の概要は準備中です。原文の説明を表示しています。

Use when contributing to Tel-Agent - picking an issue to work on, setting up the repository for the first time, starting or finishing a task, opening a pull request, or asking "what can I work on" / "how do I start" / "is my change ready to submit". Covers the full path from a fresh clone to a merged pull request.

日本語の概要は準備中です。原文の説明を表示しています。

Build the actual product — from landing page to deployed MVP with payment integration, QA testing, and post-deploy canary monitoring. Handles code generation, deployment, database setup, authentication, Stripe/payment integration, systematic QA protocol, and production health scoring. Use when the user needs to build something, deploy a product, set up payments, create a landing page, or says 'build this', 'deploy', 'create MVP', 'set up payments', or 'ship it'.

日本語の概要は準備中です。原文の説明を表示しています。

Discover profitable business ideas from scratch. Analyzes market gaps, trending niches, user skills, and competitive landscapes with a competitive intelligence protocol including 4-filter benchmark stress test and Blue Ocean differentiation grid. Use when the user has no idea what to build, wants to explore opportunities, needs market research, competitive benchmarking, or says 'find me a business idea', 'what should I build', 'market research', 'find opportunities', or 'competitive analysis'.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a deliverable markdown report by merging all /money-save snapshots for a project. Produces a shareable, dated document at ~/.smtm/reports/{project}/. Useful for sharing progress with co-founders, advisors, investors, or for personal review weeks/months later. Use when the user wants to package up accumulated state into a readable artifact. Triggered by: 'package this up', 'make me a report', 'export for partner', 'give me the deliverable', '出报告', '打包', '整理一份', '给合伙人看的'.

日本語の概要は準備中です。原文の説明を表示しています。