「automate」の検索結果

Implement policy as code with OPA, Sentinel, and Kyverno. Automate policy enforcement in CI/CD and infrastructure. Use when enforcing compliance through automation.

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

Use when creating a test plan for a blast radius. Assigns all 4 tiers (fully-automated, hybrid, agent-probe, known-gap) with exact commands, what each proves, and gap resolution options.

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

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

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

Code review and validation for CloudBase projects. After writing code for Web / miniprogram / CloudRun / cloud-function projects, call this skill to check for known pitfalls — auth guard misuse, missing database tables, RLS misconfiguration, storage domain setup, and SDK API misuse. Supports automated lint scripts (regex-based) + LLM semantic review.

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

Automated outreach and sales pipeline — cold email sequences, partnership outreach, lead generation, and prospect management. Use when the user needs cold email campaigns, sales sequences, lead generation, partnership outreach, B2B sales, or says 'cold email', 'outreach', 'lead gen', 'find prospects', 'sales sequence', or 'partnerships'.

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

Automated content creation pipeline for business growth. Creates blog posts, landing pages, email sequences, social media content, and video scripts with a supply-demand topic gate, 5-dimensional quality diagnosis, one-core resonance check, per-sentence information density scoring, 12-signal authenticity audit, headline impact matrix, content substance scoring, and a cheap-format MVP testing ladder. Use when the user needs content marketing, blog posts, email sequences, copywriting, video scripts, or says 'write content', 'blog post', 'email sequence', 'content calendar', 'marketing copy', 'video script', or 'hook'.

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

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.

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

Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a webhook, schedule a Sheets workflow, or asks 'how do I script this in Sheets'.

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

Walk through a live web app AS a real user to find usability + behavioural bugs that static reviews miss. REQUIRES proof of interaction (typing, clicking, sending, observing) before any verdict — a sweep that didn't interact terminates with verdict 'Incomplete'. Walks threads, exercises every element, runs the multi-pane stress matrix, visual polish sweep, component perfection checklist, automated a11y (axe-core), pragmatic performance budget (LCP/CLS/INP), scenario battery (11 scenarios), and stress recipes including the real-flavour data battery. Hard gates: console errors/warnings = 0, network 5xx = 0, layout collapse = 0, axe Critical/Serious = 0, perf budget green. Audit-the-audit meta-check rejects rushed reports. Each finding has reproduction steps, evidence path, and suspected code location. Trigger with 'ux audit', 'walkthrough', 'qa sweep', 'audit the app', 'dogfood this', 'check all pages', 'find what's broken', 'stress the UI'.

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

CLI syntax reference for Tabular Editor 2 (TabularEditor.exe); deployment, scripting, BPA analysis, and CI/CD integration. Automatically invoke when the user mentions "TabularEditor.exe", TE2 CLI flags (-D, -S, -A, -B, -TMDL, -O, -C), or asks to "deploy a model via CLI", "set up CI/CD for Power BI", "automate model deployment", "run BPA from command line", "save model as TMDL".

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

Writing and executing C# scripts and macros against Power BI semantic models using Tabular Editor 2/3. Automatically invoke when the user mentions "C# script", "Tabular Editor script", "TOM scripting", "MacroActions.json", "XMLA", or asks to "automate model changes", "bulk update measures", "create calculation groups", "write a macro", "format DAX expressions", "manage model metadata".

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

When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.

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

Build and run Gemini 2.5 Computer Use browser-control agents with Playwright. Use when a user wants to automate web browser tasks via the Gemini Computer Use model, needs an agent loop (screenshot → function_call → action → function_response), or asks to integrate safety confirmation for risky UI actions.

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

Use when the user gives a topic and wants an automated video podcast created, or asks to learn visual design patterns from a reference video/image. Produces 4K video via research → script → TTS → Remotion → MP4 + BGM.

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

Use when building or debugging UE5 gameplay: a character with double jump or dash, abilities with cooldowns, enemy AI that patrols, chases and attacks, a health bar or HUD; choosing Blueprint vs C++, GAS or not, StateTree vs Behavior Tree, EQS or Mass; setting up Enhanced Input, Common UI or UMG; replication, RepNotify, save games, World Partition state; "Blueprints are slow", Tick, casts and hard references; "ability won't activate", "enemy ignores the player"; or writing automated gameplay tests with injected input.

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

Use when a Scenario output must be checked and improved rather than accepted first roll: iterating a generation until it matches the brief, fixing a batch that came back off-brief, retrying failed shots methodically, wiring an automated generate, review, revise loop, or deciding whether to re-prompt, swap references, inpaint, post-process, or change model. Keywords: refine, iterate, critique, review loop, QA, self-correction, verify, acceptance criteria, retry, drift.

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

Set up Power Automate CLI prerequisites. Use when the user is new, something isn't working, or they need help getting started.

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

Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCT_EXPORT_METHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg constructor, iOS [cls new] no-arg init, requiresMainQueueSetup NO, non-throwing eager construction), so launch-time crashes surface before any build. Layer 2 validates the committed `./manifest.json` against the ppmplugin-format rules. Layer 3 asserts request/response/error-code agreement across native and PCF. Layer 4 compiles the PCF (auto-skipped if absent). Layer 5 prints a device end-to-end recipe. Native compile belongs to /build-android-binary and /build-ios-binary — this is the cheap structural pre-flight before those slow builds. Reports pass/fail per layer with a fix hint and updates .extension-state.md.

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

Manage and run Power Automate Desktop (RPA) flows and machine groups. Use when the user asks about desktop flows, RPA, or machine groups.

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

Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.

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

Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the power-automate plugin to the GitHub repository.

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

Use this skill when the user wants to enable, disable, turn on or off, opt out of, opt in to, or check the status of power-automate telemetry / usage data. Triggers: "disable telemetry", "turn off telemetry", "opt out of telemetry", "stop collecting usage data", "enable telemetry", "telemetry status".

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

Debug a failed Power Automate flow run. Use when a flow failed, has errors, or the user wants to troubleshoot a run.

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

Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.

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