agentleFS
Sign inStart free
ray5273ray5273/kr-research-kit/skills/kr-sector-analysis/SKILL.md

kr-sector-analysis

Skill2 starsChanged 8 days agoMITView on GitHub

Write Korea-focused sector and industry research in Korean. Use when the user wants a Korea sector quick brief or a full sectioned report covering market definition, market landscape, drivers, constraints, value chain, regulation, technology shifts, public-company mapping, opportunities, and risks. Use this after scoping or data-pack work when possible.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 9 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to write the final Korea sector brief or report.

    line 8
  2. Distinctive:

    Treat market metrics, policy changes, regulations, company exposure, and industry news as time-sensitive.

    line 12
  3. Very specific:

    Prefer using a scoped brief from kr-sector-plan and a fact pack from kr-sector-data-pack before drafting.

    line 13
  4. Very specific:

    If the workspace is writable, create or update analysis-example/kr-sector/<sector>.md.

    line 17
  5. Distinctive:

    Verify the latest policy, market, and company facts that matter for the conclusion.

    line 27
  6. Distinctive:

    Write the file deliverable.

    line 30
  7. Distinctive:

    Keep the markdown report synchronized with the final answer.

    line 31
  8. Distinctive:

    Read references/workflow.md for the analysis checklist.

    line 33
  9. Distinctive:

    Read references/output-format.md for the default report shapes.

    line 34
  10. Distinctive:

    Prefer official Korea sources first.

    line 39
  11. Distinctive:

    Do not force Mordor-style subsections when the source set cannot support them.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Korean Sector Analysis

Use this skill to write the final Korea sector brief or report.

Quick Start

  • Treat market metrics, policy changes, regulations, company exposure, and industry news as time-sensitive.
  • Prefer using a scoped brief from kr-sector-plan and a fact pack from kr-sector-data-pack before drafting.
  • Route the output mode early.
    • quick brief for compact decision support
    • full report for longer sectioned research
  • If the workspace is writable, create or update analysis-example/kr-sector/<sector>.md.
  • State an explicit 기준일 in the memo and keep each metric block honest about its source date.

Workflow

  1. Lock the mode. quick, brief, 한페이지, and 요약 requests map to quick brief. Broader market-structure requests map to full report.
  2. Load prior work. Reuse the planning brief and data pack when available instead of re-scoping from scratch.
  3. Refresh material facts. Verify the latest policy, market, and company facts that matter for the conclusion.
  4. Build the report. Separate verified facts from inference and keep section boundaries clean.
  5. Write the file deliverable. Keep the markdown report synchronized with the final answer.

Read references/workflow.md for the analysis checklist. Read references/output-format.md for the default report shapes.

Operating Rules

  • Open every brief and report with a 한줄요약 line directly under the title: one sentence of at most 50 characters that states the conclusion. See references/output-format.md.
  • Prefer official Korea sources first.
  • State when the sector has no clean Korea-only market-size figure in the current source set.
  • Distinguish direct exposure from thematic or second-order exposure when mapping listed companies.
  • Do not force Mordor-style subsections when the source set cannot support them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free