기타 스킬

Survey pending and required regulatory filings. Use when asked "what filings are due", "survey our regulatory filings", or "are we behind on filings".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze indicators of compromise — enrichment, attribution, and response recommendations. Use when asked to "analyze these IOCs", "enrich these indicators", or "what is this hash".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Link prospecting — pick the site's most linkable asset, find pages that plausibly link to it (resource pages, competitor linkers, unlinked mentions, broken links), verify real contact paths, and draft personalized outreach. Never invents contacts. Use when asked to "find backlink opportunities", "who should link to us", "build links to this page", "link prospecting", or "draft outreach for backlinks".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build automated regression suites — golden sets, threshold alerting, CI integration for model changes. Use when asked to "catch model regressions in CI", "build a golden set", or "automate eval regression".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Optimize similarity search — ANN index tuning, hybrid search, reranking, query expansion. Use when asked to "improve similarity search", "tune the ANN index", or "add hybrid search".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD framework", or "why are users switching".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

B2B proposal generator — takes deal context (ICP, pain, pricing tier, timeline) and produces a complete proposal document with executive summary, problem statement, solution, pricing table, implementation timeline, ROI case, and next steps. Use when asked to "write a proposal", "draft our deck for this deal", "build a proposal for this customer", or "generate a proposal".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Spec or critique custom illustrations — style, composition, and brand alignment. Use when asked to "spec an illustration", "critique this illustration", or "define an illustration style".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a forecasting model for a time series — demand, revenue, or usage prediction. Use when asked to "forecast demand", "predict next quarter revenue", or "build a time series model".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate and benchmark a forecasting model — walk-forward CV, error metrics, baseline comparison. Use when asked "is this forecast any good", "validate a forecasting model", or "backtest the forecast".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps. Use when asked to "map our AI spend", "who is spending on LLMs", or "set up AI cost attribution".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write support playbook -- response templates, issue-type runbooks, tone guide, and common resolution paths. Use when asked to "write support templates", "build a support playbook", "train our support agents", or "standardize our support responses".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.