2,719 件 ・ 関連度順
概要と使いどころ
Use when a researcher, maintainer, or contributor found or suspects a malicious skill on ClawHub and needs a private reporting workflow: opening a GitHub private vulnerability report, preparing a proposal-only PR, creating `proposals/<GHSA-ID>/clawscan.yml`, running ClawScan against the malicious skill, and explaining what evidence belongs in private versus public channels.
日本語の概要は準備中です。原文の説明を表示しています。
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
日本語の概要は準備中です。原文の説明を表示しています。
Advocate for design quality, scope, and time with cross-functional partners and leadership using evidence and shared goals.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate proposed repository harness changes with pinned Darwin tools and explicit evidence limits.
日本語の概要は準備中です。原文の説明を表示しています。
Runs evidence-aware, multi-provider research with the Librarium v2 CLI. Use for deep research, competitive research, answer-engine visibility checks, or questions needing grounded multi-source coverage.
日本語の概要は準備中です。原文の説明を表示しています。
Audit iOS/macOS apps against App Store Review Guidelines before submission, with evidence-backed verdicts and fixes. Don't use for Google Play, general code review, or rejection appeals.
日本語の概要は準備中です。原文の説明を表示しています。
Review website/app UX for humans and AX for AI/search; produce an evidence-backed audit and improvement plan across usability, brand, access, speed, conversion and discoverability. Don't use for UI builds, SEO-only edits, or legal certification.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to apply the rigorous epidemiological reasoning of Julie E. Buring (epidemiologist and women's health trialist) to study design, clinical trial critiques, cardiovascular risk assessment, and evidence-based integrative medicine. Trigger this skill whenever you are evaluating medical literature, designing cohort studies or RCTs, assessing conflicting research findings, or analyzing cardiovascular risk factors (especially in women). Reach for this when users ask about the validity of supplements, the discrepancy between observational and randomized data, or how to future-proof a clinical registry.
日本語の概要は準備中です。原文の説明を表示しています。
Status-first routing, bounded evidence collection, and safety guidance for issue-graph.
日本語の概要は準備中です。原文の説明を表示しています。
Assess nontrivial completion evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate cross-phase web execution/evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Arrange readable product screenshot evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Determine what premises and evidence warrant.
日本語の概要は準備中です。原文の説明を表示しています。
Research with scoped depth and counterevidence.
日本語の概要は準備中です。原文の説明を表示しています。
Judge claims through evidence and alternatives.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve stale facts and authority conflicts.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate rendered behavior and state evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Context-aware line edit that strips generic AI writing patterns without flattening the author's voice, plus a findings-only audit mode that names issues instead of rewriting. Applies contextual rules rather than blanket bans on adverbs, passive voice, and punctuation, and locks facts, numbers, quotes, code, links, and the supplied house style before it touches a sentence. Use before copy, a README, an email, a social post, or a doc ships; after a long assisted-writing session; when the text sounds fine but feels generated; or when the user asks for a findings-only slop audit. NOT FOR: writing new copy from scratch; deciding whether a person or a model wrote text; changing or certifying facts, which must be checked against primary evidence before publication.
日本語の概要は準備中です。原文の説明を表示しています。
Suede Labs skill that lints a local music or media release folder and scores it for release readiness: missing files, weak or malformed metadata, artwork and stem problems, split gaps, rights blockers, and platform-delivery issues, produced by a bundled offline script as a scored markdown and JSON report. Use when a creator has one or more release folders of tracks, artwork, and stems and wants to know what is missing before distributing, delivering, or handing it off; when metadata quality or a delivery rejection is the question; or when a release-readiness score is asked for. Reports what is present, missing, or unknown; never upgrades unknown to confirmed and never means legal clearance. NOT FOR: organizing the evidence behind a rights or split gap the report surfaces (use suede-rights-audit); building the transfer package (use suede-rights-passport); a sync one-sheet (use suede-sync-packaging).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-owned SEO and generative-search audit discipline. Runs a nine-lane evidence-based audit: access, intent, metadata, structure, supported schema, E-E-A-T, clusters, and exact rewrite fixes. Use when a page or site needs a deep standalone SEO/AI-visibility audit with scored lanes. NOT FOR: a fast A-F launch-appeal grade (use suede-visibility-grader); conversion-path rework after the audit (use suede-site-alchemy); getting cited by ChatGPT/Perplexity/AI Overviews (use suede-ai-seo).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-owned prospecting and qualification discipline. Use when defining an ICP, sourcing and enriching a bounded lead list, finding early adopters or design partners, scoring account fit, or documenting disqualification evidence. NOT FOR: sending outreach (use suede-cold-email), changing CRM routing (use suede-revops), or profiling competitors instead of prospects (use suede-competitor-profiling).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-affiliated comprehensive marketing planning across acquisition, activation, retention, referral, and revenue, sized to the actual team, budget, evidence, and stage. Use when the user needs a 90-day plan, 12-month roadmap, growth plan, or go-to-market operating document. NOT FOR: isolated channel execution (use the relevant public Suede skill), uncommitted tactic brainstorming (use suede-marketing-ideas), or positioning discovery alone (use suede-product-marketing).
日本語の概要は準備中です。原文の説明を表示しています。
Suede AI findings-only code review with full context: changed files, callers, contracts, and deploy surface. Covers TypeScript, React, Next.js, database, Swift/iOS, OWASP, accessibility, SEO, observability, commit hygiene, and deploy risk, ranked P0-P3 with file:line evidence and a fix path. Use when asked to review a diff, PR, branch, or commit range, find the bugs before merge, check a change for security or accessibility problems, or judge whether a change is safe to deploy. Emits findings and a ship gate, not a grade. NOT FOR: the A-F letter grade alone (use suede-code-grader); findings plus grade in one pass (use suede-code); making CI enforce the result on every merge (use suede-ci-gate); root-causing a live bug or failing test (a private Suede Labs companion, not in this pack).
日本語の概要は準備中です。原文の説明を表示しています。
Suede-affiliated ethical application of behavioral science to marketing decisions, including framing, anchoring, social proof, loss aversion, choice architecture, and friction. Use when the user needs a named psychological model, an evidence-aware application, and a testable hypothesis. NOT FOR: clinical or mental-health advice, deceptive dark patterns, page implementation (use suede-site-alchemy), or pricing design (use suede-pricing).
日本語の概要は準備中です。原文の説明を表示しています。