kr-sector-compare
Skill2 starsChanged 8 days agoMITView on GitHub
Compare Korea-focused sectors, sub-sectors, or adjacent themes on a common date basis. Use when the user asks which Korean sector has better structure, stronger policy tailwinds, cleaner listed exposure, more attractive risk-reward, or clearer near-term positioning. Do not rewrite the task as a single-sector long report.
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-data-packSkill
- 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
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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 for side-by-side Korea sector comparison work.
- Very specific: line 15
If the workspace is writable and the user wants a reusable artifact, write it to analysis-example/kr-sector/<sector-a> vs <sector-b>.md.
- Distinctive: line 22
Use the same source window and same comparison date.
- Distinctive: line 28
Read references/workflow.md for comparison rules.
- Distinctive: line 29
Read references/output-format.md for the default output shape.
- Distinctive: line 33
Keep the comparison on a same-date basis.
- Distinctive: line 35
Avoid turning a compare request into two isolated mini-reports.
≈ “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 Compare
Use this skill for side-by-side Korea sector comparison work.
Quick Start
- Normalize both sectors to the same date and source hierarchy before comparing.
- Compare only a few metrics that actually matter for the two sectors.
- Explain why the sectors deserve different treatment instead of forcing false symmetry.
- If the workspace is writable and the user wants a reusable artifact, write it to
analysis-example/kr-sector/<sector-a> vs <sector-b>.md.
Workflow
- Define the pair. Clarify what each sector label means and where the overlap ends.
- Set the common comparison frame. Use the same source window and same comparison date.
- Compare the structure. Cover demand visibility, regulation, capital intensity, listed exposure quality, and key risks.
- Rank cautiously. End with best structural setup, cleanest listed exposure, and best near-term risk-reward when the evidence supports it.
Read references/workflow.md for comparison rules. Read references/output-format.md for the default output shape.
Operating Rules
- Keep the comparison on a same-date basis.
- Say where metrics are not directly comparable.
- Avoid turning a compare request into two isolated mini-reports.
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.