Plan, verify, implement, and deliver repository work through evidence-backed ownership and quality gates.
日本語の概要は準備中です。原文の説明を表示しています。
2,234 件 ・ 関連度順
概要と使いどころ
Plan, verify, implement, and deliver repository work through evidence-backed ownership and quality gates.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose a reproducible failure, fix its cause, and verify the regression. Use for crashes, incorrect behavior, and failing tests.
日本語の概要は準備中です。原文の説明を表示しています。
Installs Scenic, the probabilistic scenario description language, for the CARLA in use — pip installing it into the same interpreter that holds the CARLA client, optionally cloning the upstream repo for the example scenarios the wheel does not ship, and verifying that the `scenic` CLI, the client and Scenic's version-keyed blueprint table all agree. Use when the user asks to "install Scenic", "set up Scenic", "download Scenic", "pip install scenic", wants to run `.scenic` files, or has a Scenic whose model import or blueprint lookup fails.
日本語の概要は準備中です。原文の説明を表示しています。
Full adversarial quality loop — implement, self-attack, parallel verification, quality gates, final validation. 全品質循環:實現、自攻、並行驗證、質量關卡、最終確認. Use when: implement task with quality, run adversarial review, verify code quality, run quality gates, complete workflow task
日本語の概要は準備中です。原文の説明を表示しています。
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to add a data source, add a connection, add an API, add a connector, connect to SharePoint / Dataverse / SQL / Excel / OneDrive / Teams / Office 365, or any similar request to make new data available to the app. DO NOT USE WHEN the user is asking to list or describe existing data sources — call list_data_sources or list_apis directly instead.
日本語の概要は準備中です。原文の説明を表示しています。
Quality review ads before launch by verifying hook strength, checking proof elements, evaluating CTA effectiveness, and assessing visual quality and authenticity. Use as final check before launching creative or when reviewing team submissions.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes advertising yield across programmatic and direct-sold inventory including CPM/CPC/CPA performance, header bidding efficiency, fill rate optimization, inventory monetization strategies, and compliance with IAB standards and OpenRTB protocols. USE THIS SKILL WHEN: - You need to audit ad revenue performance or diagnose yield drops - Someone asks about header bidding configuration or Prebid.js optimization - You are analyzing fill rates, eCPM trends, or ad unit performance - A project involves programmatic advertising, SSP integration, or ad serving - You need to verify ads.txt, sellers.json, or supply chain compliance - Someone mentions CPM floors, bid density, or auction dynamics - You are evaluating ad quality controls, viewability, or ad-related UX impact - A codebase integrates Google Ad Manager, AdMob, Prebid, or any SSP TRIGGER PHRASES: "ad yield", "eCPM", "fill rate", "header bidding", "Prebid", "programmatic ads", "ad monetization", "CPM optimization", "ad revenue", "ads.txt", "ad serving", "SSP", "ad unit performance", "viewability"
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate accessibility and WCAG compliance of UI components and pages. Use when the user asks to "check accessibility", "audit a11y", "WCAG review", "screen reader test", or needs to verify inclusive design practices.
日本語の概要は準備中です。原文の説明を表示しています。
[32] ANALYZE. Ensure every critical claim has verifiable evidence with confidence levels. Each fact must have source + confidence percentage. If confidence <85%, enter Loop150 to find more sources. Use for critical decisions, factual claims, legal/compliance work, or any situation where unverified claims are dangerous.
日本語の概要は準備中です。原文の説明を表示しています。
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Run a health check on an existing project: dependency audit, security scan, test runner detection, CI/CD evaluation, and missing configuration analysis. Maps the three execution gates (pre/in/post) from /10x-bootstrapper to an assessment framework for existing codebases. Reads optional context/foundation/stack-assessment.md from /10x-stack-assess to focus checks on identified gaps. Writes context/foundation/health-check.md with findings, prioritized fixes, and an agent-readiness verdict. Use when the user has an existing project and wants to verify its health before working with an agent. Trigger phrases: "health check", "check my project", "audit my project", "is my project healthy", "sprawdź projekt", "audyt projektu", "health-check", "project health". Use AFTER /10x-stack-assess (brownfield chain), BEFORE agent onboarding (m1-l4).
日本語の概要は準備中です。原文の説明を表示しています。
MANDATORY deploy after every code change. Typecheck → deploy → purge CDN → E2E on production → visual verify → fix-forward loop. Workers Builds native CI/CD, D1 Time Travel PIT recovery, D1→R2 long-term backups, wrangler rollback, wrangler secrets management, structured observability, cross-browser smoke tests, rollback procedures, and GitHub auto-configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Build kokoro-js-jp and run its real-browser e2e suite (Worker + WASM openjtalkjs g2p + ONNX kokoro-js synthesis, English and Japanese). Use when asked to verify this package actually works in a browser, to check whether a change broke synthesis, or to add browser-level regression coverage for a bug in the g2p/synthesis pipeline that vitest's pure-function tests can't catch. Not for typecheck/lint/unit-test requests — use npm run typecheck / npm test for those.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating new skills, editing existing skills, or verifying skills work before deployment
日本語の概要は準備中です。原文の説明を表示しています。
Research a specific company before applying or interviewing by gathering facts from primary and official sources, recording the source and date behind every claim, and keeping anonymous or unverifiable material clearly separated from confirmed fact. Use when a user asks what a company actually does, how it makes money, what its published conditions are, whether a posting matches the company's own disclosures, or what to verify before an interview; do not use to predict hiring outcomes, to repeat review-site content as fact, or to bulk-crawl sites that prohibit automated access.
日本語の概要は準備中です。原文の説明を表示しています。
Interact with challenge widgets in an authorized automation flow using checkbox clicks, slider drags, text OCR, and image-grid input. Verify completion with an application-specific condition.
日本語の概要は準備中です。原文の説明を表示しています。
Check whether a Playwright, Puppeteer, Selenium or CDP-driven browser presents a coherent fingerprint, using liarjs as a library against a Page you already have - navigator.webdriver, HeadlessChrome tokens, worker versus main-thread identity, patched-API integrity, WebGL versus WebGPU GPU identity. Use when asked whether an automated browser looks like a normal one, when a headless setup or a stealth plugin's effect needs measuring rather than assuming, or when an assertion on fingerprint quality belongs in a test suite.
日本語の概要は準備中です。原文の説明を表示しています。
Validate alignment quality with insert size distribution, proper pairing rates, GC bias, strand balance, and other post-alignment metrics. Use when verifying alignment data quality before variant calling or quantification.
日本語の概要は準備中です。原文の説明を表示しています。
Select, document, download, and checksum-verify the most appropriate NCBI reference genome on an HPC cluster. Use whenever an analysis needs a reference genome, genome FASTA, genome annotation, assembly accession, or genome index and no exact approved assembly is already available; when a user asks to fetch a species genome from NCBI; or when a pipeline must resolve and cache a reproducible reference assembly on a remote cluster.
日本語の概要は準備中です。原文の説明を表示しています。
Provider account and authenticator setup through Matrx Vault. Use when creating a service account, saving its login, enrolling 2FA, or verifying agent sign-in with Vault credentials.
日本語の概要は準備中です。原文の説明を表示しています。
Performs simple mutation testing to verify test coverage and assertions.
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively detects and auto-fixes technical debt in a codebase using three quality criteria from debt-analysis references: conditional branch simplification, encapsulation, and separation of concerns. Applies fixes directly to code, runs existing tests to verify no regressions, re-analyzes, and loops until all high-severity issues are resolved or max iterations (5) reached. Use this skill when you want to automatically improve code quality with real code changes, reduce technical debt systematically, or clean up code to meet quality standards. Trigger on phrases like "fix technical debt", "clean up code quality", "refactor and fix issues", "improve code quality automatically", "apply debt fixes", "fix code problems", "eliminate debt".
日本語の概要は準備中です。原文の説明を表示しています。
Azure Key Vault Keys Java SDK for cryptographic key management. Use when creating, managing, or using RSA/EC keys, performing encrypt/decrypt/sign/verify operations, or working with HSM-backed keys.
日本語の概要は準備中です。原文の説明を表示しています。
Find and evaluate influencers for brand partnerships, verify authenticity, and track collaboration performance across Instagram, Facebook, YouTube, and TikTok.
日本語の概要は準備中です。原文の説明を表示しています。