비즈니스 스킬

Create quarterly earnings reports for companies already being followed. Compare results with market expectations, explain differences, revise forecasts, and assess the investment case in a Word document with charts, summary tables, and linked sources.

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

• Writing a report after a quarterly earnings release
• Explaining results above or below market expectations
• Revising forecasts after new company guidance

Turn conversation logs, meeting notes, task records, and other OpenViking materials into daily Markdown reports. The skill separates confirmed outcomes from plans, consolidates repeated evidence, and links reported progress, decisions, blockers, and commitments to their sources.

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

• Preparing an end-of-day work report from scattered records
• Combining meeting notes and chat logs into a daily summary
• Separating confirmed results from agent plans and suggestions

Draft self-assessments, peer reviews, and feedback for managers using concrete examples of work and collaboration. Organizes achievements around context, actions, and results, matches your writing voice, and flags sections that need more evidence or detail.

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

• Prepare an annual or mid-year self-assessment
• Draft a peer review with specific examples
• Write constructive feedback for a manager

Plan enterprise customer onboarding from contract handoff through rollout and continued use. Provides four phases, readiness checklists, ownership checks, and adoption measures to address stalled communication, weak pilot usage, and declining engagement after launch.

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

• Plan onboarding for a new enterprise customer
• Clarify customer ownership before kickoff
• Investigate stalled communication during implementation

Design a partner program by defining value for your company, partners, and shared customers. Provides frameworks for partner tiers, phased pilots, joint marketing, and build-versus-partner decisions, with explicit measures for expanding or ending a partnership.

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

• Designing partner tiers and support levels
• Deciding whether to build internally or partner
• Defining pilot metrics and expansion criteria

Plan programs that help developers adopt an API or platform. Compare open and curated ecosystems, map the developer journey, and organize documentation, community support, partnerships, and student programs around actual product usage.

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

• Choosing an open or curated integration marketplace
• Reviewing the journey from first API call to production
• Defining community and paid support responsibilities

Plan how users discover, try, and pay for a product through self-service. Compare product-led growth with sales-led approaches, improve the first useful experience, assess acquisition channel economics, and identify when sales support should step in.

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

• Choose between product-led and sales-led growth
• Improve the first useful product experience
• Review free-to-paid conversion

Plan pricing for APIs, SaaS, and developer tools using customer value and service costs. Compare pricing models, define free tier limits, structure enterprise offers, and assess when and how to raise prices.

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

• Compare seat, usage, outcome, and hybrid pricing
• Set boundaries between free and paid plans
• Prepare enterprise pricing discussions and options

Rank problems and proposed fixes using four scored criteria: expected benefit, implementation cost, deployment ease, and risk. The skill produces a sorted priority table with scoring rationales and explains why the top three items should come first.

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

• Prioritize fixes from audit findings
• Rank improvement actions after a retrospective
• Sequence risk mitigation measures

Design meeting schedules, weekly metric reports, and quarterly planning for growing companies. Clarify who makes decisions, assign owners to priorities, and structure written updates so teams can coordinate work and reserve meetings for issues needing discussion.

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

• Redesign meetings that fail to produce decisions
• Standardize weekly business metric reports
• Align quarterly priorities and resources across teams

Plan complex enterprise sales by mapping stakeholders, checking qualification with MEDDICC, a framework for assessing deals, and building shared action plans. Review buyer alignment, purchasing steps, and customer participation to identify stalled opportunities and next actions.

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

• Planning a long enterprise sales cycle
• Mapping decision makers and stakeholder motivations
• Building a shared action plan with customer owners and deadlines

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

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

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Structure board meetings and investor updates around business progress, risks, and decisions. Use clear narrative frameworks, consistent metrics, and advance briefings to explain missed targets, present recovery plans, and make specific requests for support.

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

• Prepare a board meeting agenda and advance reading materials
• Draft a monthly investor update
• Explain missed targets and recovery plans

Plan how to sell AI products to enterprises, from product messaging and variable pricing to failure accountability. Use practical frameworks to structure demos, address operational concerns, and identify buyers prepared to adopt AI agents.

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

• Choose how to describe an AI product
• Compare pricing models for variable AI usage
• Address responsibility for AI failures

Organize Power Automate flows by business impact and responsible team using FlowStudio’s cached records. Find resources without active owners, audit connections to other services, review compliance metadata, and configure notifications for failures or missing runs.

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

• Review flows for missing governance information
• Find resources owned by departing employees
• Audit connectors and premium license needs

Plan a new product launch around finding early customers, guiding their first use, and running short experiments. The skill also helps diagnose stalled adoption, document repeatable outreach methods, and assess whether customer demand supports further expansion.

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

• Finding the first customers for a new product
• Diagnosing weak adoption after launch
• Planning two-week experiments

Use a constructive thinking partner to review assumptions, separate evidence from interpretation, and test alternative explanations. Refine conclusions and wording so claims match the available evidence and support decisions under uncertainty.

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

• Checking assumptions before an important decision
• Reviewing whether evidence supports a conclusion
• Testing alternative explanations and counterexamples

Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.

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

• Create an architecture blueprint for a new D365 implementation
• Define implementation scope and rollout phases
• Compare data migration and integration approaches

Create a feature PRD, a product requirements document, from a parent Epic. Turns a feature idea into user stories, explicit requirements, acceptance criteria, and scope boundaries that engineering teams can use to prepare a technical specification.

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

• Turn a feature within an Epic into a detailed PRD
• Describe primary user paths and edge cases
• Define acceptance criteria for feature completion

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

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

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Turn work history into clear accomplishment statements for performance reviews, promotion cases, and weekly updates. Use Copilot CLI sessions, git commits, and GitHub pull requests to connect each action with its result and supporting evidence.

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

• Recovering work accomplishments missing from a personal log
• Preparing evidence for a performance review
• Organizing achievements for a promotion case

Turn a broad product idea into an Epic PRD, a requirements document for a large initiative. Defines users, workflows, business requirements, success metrics, and scope to give engineering teams a basis for technical architecture planning.

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

• Turn a broad SaaS idea into an Epic PRD
• Define target users and their main workflows
• Clarify requirements, success metrics, and exclusions

Retrieve GitHub Copilot usage for an organization or enterprise through the GitHub CLI and REST API. Summarize active users, suggestion acceptance, and chat activity, with aggregate results or per-user tables for selected dates.

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

• Check Copilot adoption across an organization
• Review suggestion acceptance rates and chat usage
• Compare usage across individual users

Turn an unclear idea into linked decision tickets on a repository’s issue tracker. Work through one decision per session, record outcomes and dependencies, and prepare a brief defining the objective, scope, and exclusions for delivery.

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

• Clarifying the destination of an early idea
• Mapping decisions and their dependencies
• Resuming unresolved decisions across sessions