「audit」の検索結果

Run ship-safe security and quality audit on the current project. Executes npx ship-safe audit . and reports findings by severity. Use before shipping any feature or PR.

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

Audit a MaaFramework/Maa-series project's Git history to learn how Pipeline JSON, interface options, Python AgentServer CustomAction code, and related data tables evolved. Use when asked to review a Maa project from initial commit through a target commit, map `action: Custom` pipeline nodes to `@AgentServer.custom_action(...)` implementations, find pipeline/custom/option patterns or breakages, and produce a report plus skill-improvement recommendations.

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

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when the task involves `improve accessibility`, `a11y audit`, `WCAG compliance`, `screen reader support`, `keyboard navigation`, or `make accessible`.

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

Audit Orchestrator

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

Use when the user asks for a read-only, actionable audit of Python code quality, modernization, maintenance burden, ecosystem opportunities, or Pythonic design across a PR, git diff, staged/unstaged changes, files, or directories.

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

Evaluate a single skill's quality against its stated purpose. Classifies the skill's purpose type, then scores applicable quality categories — universal dimensions always apply; structural dimensions (scripts, references, assets) are scored only when warranted by the skill's purpose. A focused 20-line behavioral skill with no bundled resources scores fully on all applicable categories. Use when auditing skill quality, checking marketplace readiness, evaluating skill completeness, performing pre-publication evaluation.

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

Audit documentation claims against implementation and authoritative repository evidence. Use when checking whether README, architecture, configuration, API, usage, or feature documentation is stale, incomplete, contradicted by code, missing implemented behavior, or inconsistent with a normative contract.

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

Drafts or audits a scientific paper’s introduction and framing — the real-world "why", an evidence audit, the funnel from theory to a falsifiable if-then with a named estimand, bridges across experiments, and a contribution list matched to the design. Use when the user asks to write, restructure, or critique an introduction, motivate or frame a paper, repair a gap-in-the-literature opening, sharpen or calibrate a contribution claim, or connect experiments into one argument. Sentence-level flow and wording are out of scope.

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

Scaffolds or audits a research-project repository organized around its source library (original PDFs, tracked Markdown conversions, drop zone, bibliography, intake pipeline) plus the analysis, manuscript, and review folders the project type needs. Use when starting, structuring, or auditing a research repo or its sources folder. Single-PDF intake goes to process-source, replication packages to replication-package.

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

Audits fielded survey-response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and produces an appendix-ready quality report. Use at soft launch before full field, after fielding before outcomes are analyzed, or when asked what a study did about bots and AI respondents.

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

Drafts or audits a scientific paper's introduction: real-world motivation, evidence audit, theory-to-if-then funnel with a named estimand, bridges across experiments, and calibrated contributions. Use to write, frame, or critique an introduction.

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

Scaffold or audit a research-project repository organized around its source library (PDFs, Markdown conversions, bibliography, intake pipeline) plus the analysis, manuscript, and review folders it needs. Use when starting or auditing a research repo. Not for one-PDF intake or publication replication packages.

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

Audit fielded survey response data for registered elements, data quality, bot and AI-automation screening, and sample integrity, and emit an appendix-ready quality report. Use at soft launch or after fielding, before outcomes are analyzed.

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

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.

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

Operate or audit a live Qualtrics survey via the v3 APIs without breaking fielding: publish gating, quotas, flow routing, embedded data, panel-vendor redirects, read-back verification, and a read-only pre-fielding audit. Use when publishing or patching a fielding instrument, when a quota counts but never blocks, or before launch.

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

Scaffold or audit a social-science replication package, and audit the manuscript and archived research objects against FAIR. Use when setting up or repairing a package, checking one before submission, or drafting data, code, and materials availability statements. Adapted from Yusaku Horiuchi's replication-package-guide.

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

Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions, independently verify proposed fixes, and ship improvements in clean, focused batches. Use before cutting a release.

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

Complete DataForSEO API integration for SEO data and analysis. Use when the user asks for keyword research, search volume, SERP analysis, backlink audits, competitor analysis, rank tracking, domain authority, technical SEO audits, content monitoring, Google Trends, or any SEO-related data queries. Covers all DataForSEO APIs including SERP, Keywords Data, DataForSEO Labs, Backlinks, OnPage, Domain Analytics, Content Analysis, Business Data, Merchant, App Data, and AI Optimization APIs. Outputs CSV files.

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

When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.

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

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

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

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

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

Dependency management guidelines for Jarvy - crate selection criteria, feature flag best practices, version management, security auditing with cargo-audit and cargo-deny.

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

Audit codebase for agentic layer coverage and identify gaps. Use when assessing agentic layer maturity, identifying investment opportunities, or evaluating primitive coverage.

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

Use this skill when architecting new Claude Code agents following Anthropic best practices. Guides through YAML frontmatter creation, agent structure definition, role boundaries, and validation. Critical for creating minimal agent files (~150 lines) with proper skill invocations. Examples: <example>Context: User wants to create a new agent for security auditing user: "Create a security-auditor agent" assistant: "I'll use the agent-creator skill to build this agent following Anthropic best practices" <commentary>New agent creation requires the agent-creator skill to ensure proper structure and YAML frontmatter.</commentary></example> <example>Context: Existing agent file is too verbose and needs refactoring user: "The architect agent is 2000 lines, refactor it to minimal structure" assistant: "I'll use the agent-creator skill to refactor this into a minimal ~150 line agent with a separate skill file" <commentary>Agent refactoring requires the agent-creator skill to separate identity from technical procedures.</commentary></example>

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