「opportunities」の検索結果

Build evidence-backed SEO keyword insights and strategy using SandBase-managed search, keyword, site-analysis, and SERP capabilities. Use when asked to discover or prioritize keywords, assess search demand or ranking feasibility, map intent and topics, find competitor gaps, plan organic-search landing pages or content, or analyze a website's SEO opportunities.

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

Discover evidence-backed customer language, pain points, objections, and buying triggers from relevant Reddit communities. Use when asked for Reddit research, voice-of-customer analysis, audience pain points, product feedback, or community-led content opportunities.

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

Calculate TAM/SAM/SOM for market opportunities using top-down, bottom-up, and value theory methodologies. Use this skill when sizing markets, estimating addressable revenue, validating market opportunity for a new venture, or building investor-ready market analysis for a startup pitch or business plan.

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

Find and prioritize ethical backlink and digital-PR opportunities using SandBase DataForSEO backlink data. Use when asked to analyze backlink profiles, find referring-domain gaps, compare link competitors, or prepare a link-outreach target list.

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

Analyze competitor content coverage and uncover differentiated content opportunities using web search, page extraction, and DataForSEO content analysis. Use when asked for competitor content research, editorial gap analysis, content brief inputs, or topic whitespace.

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

Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap/site-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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

Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.

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

Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.

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

Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs.

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

Review code changes for bugs, regressions, convention violations, and high-value cleanup opportunities. Use for diffs, commit ranges, hosted PR/MR URLs, branches, paths, staged changes, or working-tree changes.

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

Expert in running effective incident postmortems. Covers blameless analysis, root cause investigation, action item prioritization, and building a learning culture. Understands that incidents are opportunities to improve systems, not punish people. Use when "postmortem, incident review, what went wrong, root cause, blameless, outage, post-incident, " mentioned.

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

Expert in building portfolios that actually land jobs and clients - not just showing work, but creating memorable experiences. Covers developer portfolios, designer portfolios, creative portfolios, and portfolios that convert visitors into opportunities. Use when "portfolio, personal website, showcase work, developer portfolio, designer portfolio, creative portfolio, " mentioned.

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

The systematic discipline of reviewing AI-generated and human-written marketing content for quality, accuracy, consistency, and effectiveness. This isn't proofreading—it's strategic quality control that catches issues before they damage brand, waste spend, or miss opportunities. In an era where AI can generate content at scale, QA becomes the bottleneck— and the moat. Speed without quality is just fast failure. Every piece of content is a brand promise, and QA ensures that promise is kept. Content QA operates at multiple levels: tactical (spelling, grammar), strategic (message alignment), technical (platform compliance), and brand (voice, tone). The best QA catches what the creator couldn't see because they were too close. Use when "review content, QA, quality check, proofread, check copy, content review, brand compliance, verify content, fact check, review before publish, content approval, final review, qa, content-review, quality-assurance, brand-compliance, proofreading, content-quality, review" mentioned.

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

Content topical authority and gap analysis powered by the DataForSEO Labs API. Clusters a domain's ranked keywords into topics, identifies strong vs weak vs missing topic clusters versus competitors, and returns a Content Score (0-100) plus the highest-leverage content opportunities to write next.

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

Find keywords competitors rank for that you don't, via the DataForSEO Labs domain_intersection endpoint. Surfaces the highest-leverage content opportunities sorted by search volume and the competitor's ranking position, with cross-competitor consensus signals.

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

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

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

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

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

Find opportunities to add metrics and estimate numbers when exact data unavailable

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

Identify, evaluate, and prioritize design opportunities using impact-effort frameworks and strategic criteria.

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

Generate editorial calendars for blogs with topic clusters, publishing schedules, content decay detection, freshness update plans, seasonal opportunities, content mix formula, template integration, and distribution scheduling. Plans monthly or quarterly calendars optimized for SEO topic authority and AI citation freshness requirements (30-day update cycles). Use when user says "editorial calendar", "content calendar", "blog calendar", "publishing schedule", "blog plan", "content plan", "what should I write".

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

Audit any domain for orphan blog pages, map internal links across all blog posts, generate keyword-backed interlinking briefs via DataForSEO, and produce a self-contained downloadable HTML report. Invoke with the target domain as the argument.

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

Suede-owned operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).

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

Perform a comprehensive DRY (Don't Repeat Yourself) code review on a codebase. Identifies duplicated code, repeated logic, redundant patterns, and opportunities for abstraction. Use this skill whenever the user asks to review code for duplication, reduce repetition, apply DRY principles, refactor for reusability, find copy-pasted code, deduplicate logic, or audit code quality with a focus on redundancy. Also trigger when users say things like "clean up my code", "find repeated patterns", "too much boilerplate", "reduce code duplication", or "refactor for maintainability". Works on any language or framework.

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