kr-sector-data-pack
Skill2 starsChanged 8 days agoMITView on GitHub
Gather structured fact packs for Korea-focused sector and industry research. Use when the user needs market definition, source-dated market metrics, policy events, regulation changes, value-chain maps, listed-company candidates, or a clean source pack before writing a Korean sector report. Do not use for the final narrative report itself.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- kr-analyst-report-discoverSkill
- kr-analyst-report-fetchSkill
- kr-analyst-report-insightSkill
- kr-analyst-report-watchSkill
- kr-article-readabilitySkill
- kr-chatgpt-reviewSkill
- kr-daily-market-newsSkill
- kr-earnings-reviewSkill
- kr-finance-slide-claritySkill
- kr-foreign-analystSkill
- kr-market-leadersSkill
- kr-market-sentimentSkill
- kr-naver-bloggerSkill
- kr-naver-blog-publishSkill
- kr-naver-browseSkill
- kr-naver-insightSkill
- kr-order-backlog-analysisSkill
- kr-portfolio-guardSkill
- kr-portfolio-monitorSkill
- kr-research-siteSkill
- kr-sector-analysisSkill
- kr-sector-auditSkill
- kr-sector-compareSkill
- kr-sector-planSkill
- kr-sector-updateSkill
- kr-stock-analysisSkill
- kr-stock-chartSkill
- kr-stock-dart-analysisSkill
- kr-stock-data-packSkill
- kr-stock-planSkill
- kr-stock-updateSkill
- kr-strategy-backtestSkill
- kr-trade-flow-analysisSkill
- kr-web-browseSkill
- telegram-report-senderSkill
- us-daily-market-newsSkill
- us-earnings-reviewSkill
- us-sec-analysisSkill
- us-stock-analysisSkill
- us-strategy-backtestSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to assemble the inputs that a downstream sector report needs.
- Distinctive: line 12
Treat market size, growth rates, policy calendars, regulations, and company facts as time-sensitive.
- Distinctive: line 13
Prefer official and primary sources first: ministries, KOSIS, Bank of Korea, industry institutes, associations, KRX, DART, and company IR.
- Distinctive: line 14
Keep the output structured.
- Very specific: line 15
If the workspace is writable, write the pack to analysis-example/kr-sector/<sector>-data-pack.md when the user asked for a reusable …
- Distinctive: line 20
Start from the agreed sector definition and note what the pack must and must not cover.
- Distinctive: line 24
Put the exact date next to each metric block or bullet when refresh cycles differ.
- Distinctive: line 28
Use markdown tables or JSON-like blocks that a downstream writer can reuse without re-parsing.
- Distinctive: line 30
Read references/workflow.md for the data-gathering checklist.
- Distinctive: line 31
Read references/output-format.md for the default pack shape.
- Distinctive: line 36
Keep conflicting source dates visible instead of flattening them into one fake reference date.
- Distinctive: line 38
Do not convert a thin source set into a confident market forecast.
≈ “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.
Files
Korean Sector Data Pack
Use this skill to assemble the inputs that a downstream sector report needs.
Quick Start
- Treat market size, growth rates, policy calendars, regulations, and company facts as time-sensitive.
- Prefer official and primary sources first: ministries, KOSIS, Bank of Korea, industry institutes, associations, KRX, DART, and company IR.
- Keep the output structured. The point is to gather clean inputs, not to write a long narrative.
- If the workspace is writable, write the pack to
analysis-example/kr-sector/<sector>-data-pack.mdwhen the user asked for a reusable artifact.
Workflow
- Define the pack scope. Start from the agreed sector definition and note what the pack must and must not cover.
- Gather dated facts. Collect the latest source-backed metrics, policy dates, regulations, value-chain facts, and public-company references.
- Label source freshness. Put the exact date next to each metric block or bullet when refresh cycles differ.
- Separate facts from interpretation.
Include only light context. Save the thesis-heavy narrative for
kr-sector-analysis. - Deliver a reusable pack. Use markdown tables or JSON-like blocks that a downstream writer can reuse without re-parsing.
Read references/workflow.md for the data-gathering checklist. Read references/output-format.md for the default pack shape.
Operating Rules
- Say when Korea-only market size is not separately disclosed.
- Keep conflicting source dates visible instead of flattening them into one fake reference date.
- Distinguish listed companies, private operators, and policy institutions clearly.
- Do not convert a thin source set into a confident market forecast.
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
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.