Kr sector plan

Skill ray5273/kr-research-kit/skills/kr-sector-plan

Scope Korean sector and industry research before drafting. Use when the user needs to define the exact sector, coverage boundary, time horizon, decomposition axes, deliverable mode, or research questions for a Korea-focused sector report, brief, comparison, or update. Do not use for writing the final sector report itself.From its SKILL.md

Install

npx -y skills add ray5273/kr-research-kit --skill kr-sector-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

Korean Sector Plan

Use this skill to turn a vague Korea sector request into an execution-ready research brief.

Quick Start

Define the exact sector first. Resolve whether the user means a product category, a value-chain slice, a policy theme, or a listed-company basket.
Lock the output mode early: quick brief, full report, comparison, audit, or update.
Keep the deliverable to planning. Do not drift into writing the actual report or filling in unsupported numbers.
If the workspace is writable and the user wants a reusable planning artifact, write the brief to analysis-example/kr-sector/<sector>-리서치브리프.md.

Workflow

Clarify the target sector. Normalize the user's wording into a sector definition that another agent can execute.
Set the report boundary. Pin geography, time horizon, value-chain depth, end-market slices, and whether listed-company coverage is required.
Choose the output mode. Route the request into quick brief, full report, comparison, audit, or update.
List the key questions. State what the downstream research needs to answer, what can be omitted, and which assumptions are allowed.
Hand off cleanly. Produce a short research brief and tailored outline that downstream sector skills can consume directly.

Read references/workflow.md for planning rules. Read references/output-format.md for the required brief shape.

Operating Rules

Prefer narrowing the scope over pretending the sector boundary is obvious.
Separate user intent from your assumptions.
Flag where the sector name overlaps with adjacent themes such as cloud, AI infrastructure, utilities, or software services.
Avoid numeric estimates at this stage unless the user explicitly asked for a scoping estimate and provided a source.