106건 · 관련도순
Check investment research for bias before searching and before writing conclusions. A short checklist broadens coverage beyond large companies and English sources, challenges bullish assumptions, and checks whether important figures are current.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop an eight-part article series examining one company's competitive strengths, earnings, assets, management, and valuation. Review figures, sources, accounting definitions, and claims across the series to prepare consistent articles for public publication.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess a company’s management through public statements, delivered commitments, crisis decisions, and use of company funds. Produce evidence-based scores for integrity, strategy, capital allocation, and governance, alongside a verdict on long-term trust.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a sales opportunity using deal records, emails, and meeting notes. Get an evidence-based assessment of closing likelihood, missing information, risks, and prioritized next steps, with a comparison against the stage recorded in your sales system.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Repair an entire broken feature by mapping its files and dependencies, checking configuration and logs, and confirming root causes. Apply fixes in sequence, then test the feature and the code that uses it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Search Google SecOps events for threats that have not triggered alerts. Test attack hypotheses, check historical records for compromise indicators, and examine unusual activity, then document findings and add them to relevant security cases.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess whether a GKE cluster or application is ready for production. Coordinates specialist skills to review scaling, security, reliability, monitoring, recovery, costs, and maintenance, then reports domain status, a weighted readiness score, and remediation priorities.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Assess dependency confusion, where a build retrieves a public package instead of an intended private one. Discover internal package names, review registry settings, plan callback-based proofs of execution, and document fixes across major package ecosystems.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Analyze public-company earnings after results are released, combining reported figures, guidance, estimates, and call evidence. Produces source-backed reports that examine recurring profitability, investment implications, key business drivers, and upcoming events to monitor.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep-dive analysis of GitHub projects. Use when the user mentions a GitHub repo/project name and wants to understand it — triggered by phrases like "help me look at this project", "learn about XXX", "what is this project like", "analyze this repo", or any request to explore/evaluate a GitHub project. Covers architecture, community health, competitive landscape, and cross-platform knowledge sources.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates rich technical documentation pages with dark-mode Mermaid diagrams, source code citations, and first-principles depth. Use when writing documentation, generating wiki pages, creating technical deep-dives, or documenting specific components or systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "run a launch retro / post-mortem", "compare launch results vs targets by channel", or "decide what to keep or kill for the next launch"; produces a structured D1/W1/M1 retrospective — a per-channel actual-vs-target table (UTM-attributed own analytics as the truth column, platform self-reported numbers as reference, every figure labeled Measured / User-provided / Estimated), a 5-Whys chain on the single largest miss, keep / kill / change decisions per channel, 3-5 actionable learnings for the next launch, and an outcome snapshot submitted to the launch registry. Not for return math (CPA / ROI) — use roi-calculator; not for the stakeholder-facing report writeup — use report-generator; not for a metric deep-dive — use performance-analyzer. 发布复盘/渠道归因/5-Whys/keep-kill
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "monitor my launch", "track our Product Hunt / Hacker News ranking", or "watch the launch window"; runs the T-0 to T+30 window watch — pre-launch instrumentation verification (UTM/event checks, the upstream of RAMP P1), HN rank/points/comments polling with a comments-over-points flamewar early-warning (Estimated heuristic), PH votes/featured status, store charts and reviews, news echo, D0/W1/M1 KPI snapshots vs targets, spike-vs-sustain and owned-capture reads, and alert thresholds against the launch-tier KPI targets. Not for launch-day go/rollback calls — use launch-day-conductor; not for metric deep-dives — use performance-analyzer; not for SEO rank tracking — use rank-tracker. 发布监控/排名轮询/火焰战比/spike-sustain
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "analyze my target audience", "build an audience profile for influencer targeting", "research a niche community", or "deep-dive a subculture before partnering with creators"; in audience mode produces demographic/psychographic profiles, a platform-priority matrix, named personas, and an influencer-selection criteria set, and in niche mode produces a community map, culture decode (language/norms/taboos), key-voice tiers, a Brand Fit Score, and a phased entry strategy. Not for finding specific creators to contract — use influencer-discovery; not for scoring a shortlist on Suitability — use fit-scorer. 目标受众画像/人群分析 · 细分社群/亚文化调研
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a full AWS Well-Architected Framework review evaluating every framework question across all pillars discovered from the live AWS documentation by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation. Supports full reviews (every framework best practice with BP ID citations), quick reviews (question-level), pillar-scoped reviews, score-mode reviews (a maturity scorecard with per-pillar scores and filtered findings), and lens-specific reviews using lenses discovered from the live AWS documentation. Triggers on mentions of Well-Architected review, WA review, WAR, pillar assessment, architecture review across pillars, workload assessment, cloud readiness evaluation, or a Well-Architected score, grade, or scorecard request. Does not apply to single-pillar deep-dives, learning WA concepts, ADRs, or migration readiness assessments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive Apollo.io migration strategies. Use when migrating from other CRMs to Apollo, consolidating data sources, or executing large-scale data migrations. Trigger with phrases like "apollo migration", "migrate to apollo", "apollo data import", "crm to apollo", "apollo migration strategy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate notes between Apple Notes, Obsidian, Notion, and other platforms. Trigger: "apple notes migration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate to Claude API from OpenAI, Gemini, or other LLM providers. Use when switching from GPT-4 to Claude, migrating from Text Completions, or building a multi-provider abstraction layer. Trigger with phrases like "migrate to claude", "openai to anthropic", "switch from gpt to claude", "multi-provider llm".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and execute a reversible migration from another search system or legacy index design to Algolia. Use when translating schemas, queries, relevance behavior, or production traffic. Trigger with "migrate to Algolia", "Algolia cutover", or "search engine migration".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and execute a multi-workload migration into or across Adobe services with contract evidence, dependency waves, dual-run reconciliation, cost controls, and rollback. Use when the task requires adobe platform migration program. Trigger with "Adobe migration plan", "move workflow to Adobe", or "Adobe platform consolidation".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Claude-native deep research using DAG-based query planning, parallel subagent execution, and gap-driven iteration. No external API needed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a complete, beginner-friendly explanation of an entire code repository as a set of markdown files. Maps the repo structure with `treecap` (installing it if missing), studies the actual source, then writes a `CODE_EXPLANATION/` folder containing an `OVERVIEW.md` plus numbered deep-dive files (01_architecture.md, 02_models.md, ...) that explain how the code is built, what it does, and how the pieces fit together — illustrated with real code excerpts. Use this skill whenever the user wants to understand, document, onboard onto, or get a walkthrough of a codebase: phrases like "explain this repo", "explain the code", "code explanation", "walk me through this codebase", "help me understand how this is built", "document the architecture", or "what does this project do" — even if they don't say the word "skill". Prefer this over ad-hoc summaries whenever the goal is a durable, written explanation of a whole repo.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.