「check」の検索結果

Use when the user wants to validate, lint, or audit agent skill files (SKILL.md). Use when they say "validate these skills," "check this repo's skills," "lint SKILL.md files," or "audit skills in [repo URL]." Run skill-check locally or against a cloned GitHub repo and summarize findings.

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

Fix the currently-failing status checks on the current branch's PR in one sweep — route each failing check to the right diagnosis skill (via a Haiku subagent, escalating to Opus on a repeat failure), apply and verify the fix, commit, and push once — then return a summary. Use standalone when CI is red, or as the check-fixing step invoked by /watch-pr. Repo is adamayoung/TMDb.

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

AWS Compliance Checker workflow skill. Use this skill when the user needs Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

AWS Compliance Checker workflow skill. Use this skill when the user needs Automated compliance checking against CIS, PCI-DSS, HIPAA, and SOC 2 benchmarks and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Uses authored HTML checkpoints or bounded legacy batches, delegates each scope to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint before the next batch. The checkpointed counterpart to /sprint's autonomous run.

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

Audits any landing or service page across 48 checks in 10 categories for LLM/AI discoverability, GEO readiness, content clarity, schema markup, internal linking, freshness signals, and technical crawlability. Produces an overall score out of 100, a per-category score out of 100, pass/warn/fail/ manual counts, and a prioritised fix list — all rendered as a standalone HTML report saved to disk. Use when a user provides a URL and asks to audit it, score it, check its GEO readiness, test its AI discoverability, run a landing page audit, or evaluate it for LLM citation potential. Also trigger on phrases like "audit this page", "score this URL", "check GEO for", "is this page AI-ready", "run a GEO audit", "LLM page check", "how would AI read this page", or "landing page score".

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

Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check. Use this skill whenever a user provides a docs URL and asks to audit it, review it, score it, check its quality, or evaluate it for AI discoverability, SEO, structure, content, or completeness. Also trigger when the user says "run a docs audit", "audit these docs", "check this documentation", "how good are the docs for X", or pastes a docs URL with any evaluative intent. Always use this skill — do not attempt a freeform docs review without following this structured workflow.

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

Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and response schema completeness. Produces a polished interactive HTML report with a summary scorecard, site-wide pattern analysis, ranked top issues, and per-endpoint findings with specific fix guidance. Trigger this skill whenever a user provides a documentation URL and asks to audit, review, analyse, or check their API docs. Also trigger for: "do the same audit for X", "audit docs.company.com", "check the API docs at X", "run the API docs audit on X", "review the docs for Y API", or pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. Always use this skill — do not attempt the audit without following this structured crawl-score-report workflow.

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

Review any client-facing message or material (emails, letters, newsletters, social posts, website copy, presentations, performance reports, proposals) for compliance with SEC rules that govern investment advisers — the Marketing Rule (206(4)-1), fiduciary duty / antifraud provisions (206), Books and Records (204-2), and Reg BI where broker-dealer activity applies. Produces a pass/flag/fail markup, required disclosures, a books-and-records scratch-pad entry, and an archiving handoff reminder. Triggers on "compliance check", "/compliance", "is this compliant", "review this before I send it", "can I say this to a client", "check this email/post/deck". Use it whenever an advisor asks to check, review, or look over anything before it goes to a client or prospect — "check this before I send it", "look this over before it goes out" — even a routine note, because deciding that a message needs no changes is part of the review, not a reason to skip it.

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

Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.

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

Verify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.

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

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. What's inside: • 4-step research framework (website teardown → social media → traffic sources → ad spend) • 3-version website evolution analysis (V1 / Beta / Launch via Wayback Machine) • X/Twitter propagation chain mapping (4-phase model + single-post teardown template) • Growth flywheel 6-stage scoring system (Activation → Referral → Acquisition → Retention → Revenue → Product) • KOL identification framework (Traffic King / Topic Starter / Mindset Shifter) • Content effectiveness ranking (validated: Visual Demo > User Story > Competitor Comparison) • ICP deep analysis template + Freemium pricing teardown • Complete self-check checklist 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. Inside: 4-step research framework (website → social → traffic → ad spend) · 3-version Wayback evolution analysis · X/Twitter propagation-chain mapping · growth-flywheel 6-stage scoring · KOL identification · content-effectiveness ranking · ICP + freemium pricing teardown · self-check checklist. New in 1.2: time-machine competitor archaeology — Google date-range search back to pre-fame years, star-history launch-day reconstruction (AppFlowy ~40-channel zero-budget launch teardown), competitor funding news as a launch-timing signal, and the "open source alternative" positioning play. Sourced from first-hand founder interviews (AFFiNE co-founder, 2026-04, self-reported figures marked). 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. What's inside: • Pre-launch readiness checklist (6 conditions that must be true before starting) • 6-step community setup SOP (platform selection → rules → admin standards → monitoring → wiki → metrics) • Ambassador recruitment system (A+B qualification, application form design, scoring rubric) • 4-tier progression system (Bronze → Silver → Gold → Platinum with point thresholds) • 5-pillar incentive framework (Product quality → Beta access → Founder access → KOL path → Full engagement) • Churn early-warning system + retention playbook • Event operations SOP (6 event types × full lifecycle) • Health metrics dashboard (6 core KPIs + 5 ambassador-specific indicators) • Governance & risk control (behavior code, escalation matrix) • Real templates: recruitment post, welcome email, annual calendar 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

Debug validator checkpoint inconsistencies where some validators are behind others. Use when alerts mention "checkpoint inconsistency", "validators behind", or "inconsistent latest checkpoints", or when asked to debug validator sets, investigate validator delays, or troubleshoot metadata fetch failures for a chain. Defaults to default_ism app context if not specified.

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

The post-change validation contract for warp routes — after any step that changes (or proposes) on-chain state, prove the route's config matches the target via hyperlane warp check. Run a live check when the change already executed (deployer-signed); run a fork-simulate-from-owner check via /warp-route-check when the change is pending multisig/file execution. Referenced by every deploy/update skill that mutates a route.

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

This skill enables Claude to automatically check for HIPAA (Health Insurance Portability and Accountability Act) compliance issues in codebases, infrastructure configurations, and documentation. It leverages the hipaa-compliance-checker plugin to identify potential violations related to data privacy, security, and access controls. Use this skill when the user explicitly requests to "check HIPAA compliance", "scan for HIPAA violations", "assess HIPAA readiness", or similar phrases related to HIPAA audits and security best practices. It is useful for projects handling protected health information (PHI) and requiring adherence to HIPAA regulations.

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

Runs deterministic Python quality checks against a path or scope — formatting, linting, type checking, and typing-boundary policy. Use when checking or fixing code quality via prek, ruff, ty, pytest, or the check-typing-boundaries policy script. Reports results grouped by category; fixes only when explicitly requested.

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

Audits a manuscript's citations for fabricated or nonexistent sources, DOIs that resolve to a different work, mismatches between in-text citations and the reference list, APA 7 or journal style, and whether each source supports the claim it is attached to. Checks entries against Crossref, OpenAlex, and DataCite and labels anything it could not verify NOT CHECKED. Use to check citations, references, a .bib file, or DOIs, or when a source may be AI-invented. Figures and tables go to figure-table-audit.

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

Run the marketing harness quality gates on content. Scores Four U's (Unique/Useful/Ultra-specific/Urgent), checks for banned words and AI slop, runs SEO lint for search content. Use when "score this", "quality check", "run quality gates", "check this content", "four u's score", "banned word check", "SEO lint", or any request to validate content quality before publishing.

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

Read GitHub Actions CI for the current branch or open PR, triage failing checks, reproduce locally, and fix scoped issues until green. Use whenever the user mentions CI failures, red checks, failed pipeline, GitHub Actions, merge blocked, fix the build, babysit CI, gh run failed, ruff/ty errors, failing pytest, example run failed, or asks to check CI on this branch — even if they only paste a log snippet. Also use after implementing a feature when tests, lint, or typecheck might have broken.

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

Independent re-derivation gate for proposed changes during autonomous execution. Evaluates a change (code diff, config edit, engine evolution, schema change) against the work's authority matrix and a 4-check protocol: invariant compliance, scope authorization, detection narrowness, and regression risk. Returns structured JSON with pass/fail per check, an overall verdict (APPROVE / REQUEST_CHANGES / REJECT), and blockers. Profile-driven thresholds (strict for unattended runs, lenient for desk supervision). Use when an autonomous agent proposes an engine change, when reviewing a Claude Code-authored modification before merge, or when an unattended profile requires independent re-derivation. Trigger on: "review/approve this proposed change," "critic-gate this," "is this change safe," "is this safe to merge," "should I let this land," "run the critic." Do NOT use for handoff-readiness checks (use rootnode-handoff-trigger-check), general code review, or design-time correctness. Authority matrix required.

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

動画・画像のフレーム抽出、Remotion レンダリング、仕様チェック、目視検証を行う汎用ビデオツールキット。 ffmpeg / ffprobe / remotion still / remotion render を統一シェルスクリプト (video-tool.sh) で操作し、 Read ツール（マルチモーダル対応）で実際の見た目を確認して品質レポートを出す。 Use when: 動画のフレームを確認したい、レンダリング結果を検証したい、 画像の品質を目視チェックしたい、Remotion プロジェクトを MP4 に出力したい、 動画の仕様（解像度・fps・長さ）をチェックしたい。 Triggers: "フレーム確認", "フレーム検証", "動画チェック", "frame inspect", "フレーム抽出", "動画の中身を見たい", "レンダリング確認", "動画検証", "MP4 確認", "動画のスクショ", "frame check", "動画を出力", "Remotion render", "動画レンダリング", "仕様チェック", "spec check", "video render"

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

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