「oss」の検索結果

Pull and analyze Google Search Console data via the GSC API. Produces: weekly query × page performance with WoW/MoM/YoY deltas, top movers report (winners + losers ranked by absolute click change), click-loss attribution (lost rank? Triggers: "GSC", "Google Search Console".

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

Generate a production-grade OEE (Overall Equipment Effectiveness) measurement pipeline for a manufacturing line — data ingestion from MQTT/OPC-UA/Modbus/CSV, A×P×Q calculation engine, Six Big Losses categorizer, MTBF/MTTR/TEEP metrics, Grafana or Streamlit dashboard.

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

Generate and maintain a multi-channel product feed across Google Merchant Center, Meta Catalog (Instagram + Facebook Shops), TikTok Shop, Pinterest Catalogs, Bing Shopping, and Snapchat Catalogs from a single product source of truth (Shopify, BigCommerce, WooCommerce, custom DB)..

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

Benchmark franchise locations by comparing top and bottom quartile performance across revenue, profitability, and operational scores.

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

Monitor federal grant opportunities across Grants.gov (Simpler.grants.gov is the modern UX), SAM.gov assistance listings (the post-CFDA replacement that preserves CFDA program numbers), and direct agency portals — NIH RePORTER + NIH Guide, NSF Funding, DOE OSTI, USDA NIFA, EPA Grants.

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

Analyze game AI systems including behavior trees, finite state machines, GOAP planning, utility AI scoring, A-star and NavMesh pathfinding, steering and flocking behaviors, perception and awareness models, dynamic difficulty adjustment, NPC dialogue trees and scheduling, boss AI patterns.

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

Analyze project dependencies for health, security, and bloat — audit outdated, deprecated, vulnerable, duplicate, heavy, and unused packages across npm, pip, cargo, go mod, and more. Produce a dependency health score, CVE inventory, license compatibility matrix, bundle size impact assessment, and a prioritized update plan with migration paths.

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

Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards..

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

Track brand mentions, URL citations, and share-of-voice across the 2026 AI search surface — ChatGPT (with browsing), Perplexity, Claude (with search), Google Gemini, Google AI Overviews, Bing Copilot, You.com, Phind, and Microsoft Copilot..

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

Score your codebase 0-100 across complexity, coupling, cohesion, test coverage, documentation, churn hotspots, dependency health, and lint/type safety. Triggers: 'how healthy is this codebase', 'check code quality', 'score my project', 'find tech debt hotspots'.

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

Four-phase skill for planning and executing large-scale codebase migrations using full-context AI analysis. Produces an impact map, ordered batch plan, subagent execution protocol, and cross-codebase validation pass. Optimized for Fable 5's 1M-token context window.

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

Maps the entire API surface of a codebase -- route definitions, middleware chains, auth requirements, request/response types, deprecated endpoints, orphaned endpoints, and cross-endpoint inconsistencies..

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

Deep cross-layer consistency audit for any codebase. Traces every feature from UI to database, finds broken wiring, missing handlers, model mismatches, and security gaps. Auto-fixes critical and warning issues. Use this after building features, before releases, or whenever something feels off. Works with any tech stack.

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

Audit curriculum management software for learning outcome alignment, pacing guide optimization, standards coverage mapping (Common Core, NGSS, state standards), differentiation support, assessment design quality, and content gap detection across grade levels and subjects..

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

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..

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

Discover shadcn-compatible components and registries across the entire ecosystem before writing any custom UI. Use PROACTIVELY before building tables, forms, modals, animations, dashboards, auth pages, or any UI component. Use when the user says "find a component for...", "is there something for...", "search registries", "what exists for...", or asks about shadcn blocks, Magic UI, Aceternity, ReUI, Animate UI, DiceUI, Tailark, AI Elements, or any other shadcn-compatible registry. Complements the official shadcn skill by surfacing registries beyond the user's configured `components.json` — use when exploring what's available to add, not just what's already installed.

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

Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report

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

Allocate testing effort based on risk and failure likelihood using Google's SET/SWE/TE model. Use when user says "risk-based testing", "where should I focus testing", "test coverage strategy", "prioritize what to test", "high risk areas", or needs to decide how to distribute QA effort across a codebase - even if they don't explicitly say "risk-based".

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

Plan a monthly content calendar across channels using the Content Marketing Matrix (Dave Chaffey, Smart Insights) - Entertain/Inspire/Educate/Convince. Every post gets a quadrant label. The monthly calendar must hit 40% Educate, 40% Inspire+Convince, 20% Entertain. Produces a week-by-week posting schedule with topics, formats, channels, and asset links. Use when the user says "content calendar", "social calendar", "plan next month's content", "what should we post", "content plan", "editorial calendar", "schedule posts for the month", or wants a structured posting plan for LinkedIn, Twitter, email, or blog. Reads brand voice, ICP, and past learnings from knowledge/. For writing the individual posts, see linkedin-post, newsletter-writer or content-writer. For the campaign this sits inside, see campaign-brief. For the end-of-month review, see retro.

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

Synthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions

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

Surface and visualize hidden dependencies blocking delivery. Use when the user says "map our dependencies", "what's blocking what", "dependency audit", "why are teams blocked", "we have a bottleneck", "draw out the dependencies", or asks to identify cross-team blockers - even if they don't explicitly say "dependency mapping". Based on "Making Work Visible" by Dominica DeGrandis (time theft, invisible work, flow blockers).

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

Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.

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

Diagnose why a landing page, homepage, pricing page, or signup form is not converting, and produce a ranked fix list with a test plan. Runs a structured audit across motivation, value clarity, friction, anxiety, and CTA hierarchy rather than giving generic design opinions. Use when the user says "why isn't this page converting", "improve our conversion rate", "CRO", "conversion audit", "this page isn't working", "high traffic low signups", "people bounce", "review our landing page", or shares a URL and asks what is wrong with it. For rewriting the words only, see copy-review. For writing a new page from scratch, see landing-page-writer. For the statistics of running the test afterwards, see growth-experiment.

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

**WORKFLOW SKILL — MANDATORY for ANY hook work.** Create, configure, edit, debug, or review lifecycle hooks for VS Code Copilot (default) and Claude Code. USE FOR: criar/configurar/editar hook, hook do Copilot/Claude/agente, lifecycle hook, PreToolUse, PostToolUse, SessionStart, SubagentStop, Stop hook, UserPromptSubmit, PreCompact, bloquear comando, validar tool call, injetar contexto, guard, .agent.md frontmatter hooks, hooks.json, .github/hooks, .claude/settings.json, hook Node.js, cross-platform, hook não dispara/silencioso/ignorado, permissionDecision, hookSpecificOutput, additionalContext. **DEFAULT = VS Code GitHub Copilot.** Switch to Claude Code only when user explicitly says "Claude" OR workspace has `.claude/`. NEVER assume Claude. DO NOT USE FOR: general coding, creating agents (use agent-creator), creating skills (use skill-creator).

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