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 when the user already has a Korea sector memo and only wants what changed.

   line 8
2. Very specific:

   Start from an existing sector memo under analysis-example/kr-sector/<sector>.md.

   line 12
3. Distinctive:

   Search only for material changes after the memo date: policy updates, industry statistics, regulation changes, public-company disclosures, …

   line 15
4. Distinctive:

   Read the baseline memo. Capture the original thesis, source window, and any prior updates.

   line 19
5. Distinctive:

   Search for material developments after the memo date.

   line 22
6. Distinctive:

   Keep only what changes the thesis, risks, or monitoring list.

   line 24
7. Distinctive:

   Write the update block. Lead with what changed, what did not, and what to watch next.

   line 27
8. Distinctive:

   Read references/workflow.md for update rules.

   line 30
9. Distinctive:

   Read references/output-format.md for the dated update shape.

   line 31
10. Distinctive:

    Do not rebuild the entire report unless the new evidence clearly breaks it.

    line 35
11. Very specific:

    Prefer saying no material sector-specific update over forcing a narrative.

    line 37

≈ “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.