7.2K skills · sorted by relevance
倫理的かつ効率的な英語論文執筆を支援するスキル（水本 2025; langtech.jp/ai-writing/ に基づく）。 論文の英語化，校正，構成相談，査読対応，AI利用申告の作成を，学術的誠実性のガードレール付きで行う。 以下のような場面で必ず使用すること： 「論文の英語を直して」「英語論文を書きたい」「この段落を校正して」「査読コメントに返事を書きたい」 「AI利用の申告文を作りたい」「Introduction/Methods/Results/Discussionを書きたい」 「カバーレターを書きたい」「論文の構成を相談したい」「英文を洗練したい」 「日本語を英語にしたい」「表現の候補を出して」「時制をチェックして」 英語論文に関するあらゆる執筆支援タスクで使用する。
The English summary is being prepared. Showing the original description.
Add authorization methods for a new entity to AuthorizationService. Use after creating a resource service. Triggers on "add permissions", "authorization methods", "entity permissions", "add auth methods".
The English summary is being prepared. Showing the original description.
End-to-end bisulfite sequencing workflow from FASTQ to differentially methylated regions. Covers Bismark alignment, methylation calling, and DMR detection with methylKit. Use when analyzing bisulfite sequencing data.
The English summary is being prepared. Showing the original description.
Sort incoming scout messages and agent-forwarded openings by what they actually disclose: whether the employer is named at all, which of pay, location, employment type, and duties are stated, whether the message refers to the applicant's own history or reads as a mass send, whether a stated salary is an offer or a "up to" figure, and whether the same employer has arrived through more than one route. Use when a user has a backlog of scout messages and wants to know which ones can be researched, what to ask before replying, and what to settle before handing over a resume; do not use to rate how promising an opening is, to judge an employer or an agent, or to reply on the user's behalf.
The English summary is being prepared. Showing the original description.
Help a user talk through whether to change jobs, stay, or change something in their current work, starting from uncertainty, distress, a vague sense of stagnation, an offer in hand, a counter-offer from the current employer, or pressure from family or colleagues. Clarify what matters, separate deadlines that order the next steps from the decision itself, compare conditional options, and agree on a small next step and a time to revisit it. Use when someone asks whether they should quit, wonders whether leaving is just running away, has second thoughts after receiving an offer or being asked to stay, feels stuck because others say it would be a waste, wants to leave soon after joining, or wants advice before deciding to start a job search; do not make the final stay-or-leave decision, evaluate offer terms, plan the resignation, or predict hiring outcomes.
The English summary is being prepared. Showing the original description.
Check whether a user may start side work alongside their current job, by reading the employer's own rules and contract clause by clause: whether side work is prohibited, needs prior permission, or only a notification, and which duties the planned side work could touch (non-compete, confidentiality, exclusive attention to the main job, use of company assets and information, combined working hours). Separate what is confirmed in a document from what is hearsay, and produce the questions to ask the employer plus the facts an application or notification will need. Use when someone with a main job is considering side work, freelance or gyomu-itaku work, a second part-time job, or paid trial work for another company, and needs to know what their own employer's rules require first; do not use to rule on whether a clause is lawful or enforceable, to help conceal side work from an employer or avoid filing obligations, to predict whether permission will be granted, or to submit the application or contact the employer.
The English summary is being prepared. Showing the original description.
Cross-method decision tree for calling hits in pooled CRISPR screens. Catalogs statistical models (MAGeCK RRA, MAGeCK MLE, BAGEL2, drugZ, JACKS, Chronos, CERES), experimental designs each is built for, failure modes outside design domain, reconciliation when methods disagree, multiple-testing and effect-size thresholds, the order of operations (count -> QC -> CN-correct -> hit-call -> validate), the second-best-sgRNA conservative rule, and consensus-hit strategy. Use when choosing among MAGeCK / BAGEL2 / drugZ / JACKS / Chronos for a given design, reconciling disagreement across two or three methods on the same screen, deciding whether to require consensus, gating downstream validation by hit-confidence tier, or interpreting unstable hit lists across reruns.
The English summary is being prepared. Showing the original description.
Cross-method decision tree for calling hits in pooled CRISPR screens. Catalogs statistical models (MAGeCK RRA, MAGeCK MLE, BAGEL2, drugZ, JACKS, Chronos, CERES), experimental designs each is built for, failure modes outside design domain, reconciliation when methods disagree, multiple-testing and effect-size thresholds, the order of operations (count -> QC -> CN-correct -> hit-call -> validate), the second-best-sgRNA conservative rule, and consensus-hit strategy. Use when choosing among MAGeCK / BAGEL2 / drugZ / JACKS / Chronos for a given design, reconciling disagreement across two or three methods on the same screen, deciding whether to require consensus, gating downstream validation by hit-confidence tier, or interpreting unstable hit lists across reruns.
The English summary is being prepared. Showing the original description.
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
The English summary is being prepared. Showing the original description.
Check whether Nasiko CLI is installed, preview installation of a fixed, verified version, and remove an ECC-managed installation. The workflow uses ECC commands, requires consent for installation, and checks ownership before removal.
Review a development plan before implementation by challenging its premise, comparing alternative approaches, and examining design, security, testing, and operations. Choose whether to expand, maintain, or reduce scope, then receive a summary of agreed decisions.
Evaluate Caveman optimization observations by selecting a specific code change with operator approval. Compare the original and changed versions on identical inputs, checking both task quality and resource usage before deciding whether to keep the change.
Organize software development from requirements and architecture through testing, review, and deployment. Use specialized agent roles, shared memory, and test-driven development, where tests are written before code, to coordinate work across the project.
Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.
Manage payment administration with Stripe-compatible tools for creating and finding customers, setting up recurring subscriptions, attaching payment methods, and reviewing customer balance changes. The supplied workflows use Composio's Stripe toolkit through Rube MCP.
Review whether analytics and advertising trackers stay blocked until users consent to non-essential cookies. Check rejection, withdrawal, and access to cookie settings, and get implementation guidance tied to actual browser behavior.
Plan and review systems where several AI agents work together. Assess whether multiple agents are useful, choose roles and communication methods, and define shared files, verification, and resource limits to address conflicts, spreading errors, and uncontrolled execution.
Revisit a recent answer, plan, draft, or decision using selected critique methods. The skill offers relevant approaches, explains what they reveal, and proposes improvements that are applied only after the user accepts them.
Prepare experiments for Ginkgo Cloud Lab by choosing a protocol, organizing required inputs, checking configured pricing, and navigating browser ordering. Covers protein expression, RNA synthesis, stability assays, and setup of measurement methods.
Investigate a GitHub issue or reported problem, check whether it is a bug, and test a proof of concept. Explain the behavior changes and supporting evidence so the user can decide whether to proceed with the full fix.
Turn one scientific paper into a structured, 16-section reading card. Break down its methods, connect claims to experimental evidence, identify limitations, and develop research hypotheses, with source references and clear labels for anything the supplied material cannot support.
Review an API request against the supplied specification without sending it. Check the method, URL, headers, body, authentication format, and query parameters, then receive a brief verdict or a specific correction.
Design production alerts, route notifications by severity, and organize on-call schedules. Use configuration examples to define backup contacts, escalation steps when alerts go unanswered, and runbooks that guide responders through incident investigation.
Use natural language to compare Binance P2P offers, prices, and payment methods. Review personal orders and dispute progress, submit evidence for existing appeals, and manage advertisements when the account has the required merchant permissions.