We split this skill into the rules it gives an agent

21 rules. About 0 are common, 11 are distinctive, and 10 are 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.

• 10

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Use this skill when the task starts from an x.com or twitter.com link and the goal is to learn from it, analyze it, or turn it into a new …

   line 8
2. Distinctive:

   Do not stop at the X block screen.

   line 12
3. Distinctive:

   If direct X page fetching is blocked, continue with the best evidence already available and produce the requested output immediately.

   line 14
4. Very specific:

   Use x_tweet_fetch first for status or article links.

   line 18
5. Very specific:

   If the payload contains article_title, article_preview_text, or article_plain_text, treat that as the primary source article.

   line 19
6. Very specific:

   Only use web_fetch for non-X URLs discovered from the tweet payload.

   line 20
7. Very specific:

   Do not use direct web_fetch on x.com as the first attempt.

   line 21
8. Very specific:

   Use direct browser fallback on x.com only if Charlie explicitly asks for deeper retrieval.

   line 22
9. Very specific:

   When the visible fetch result is just the X error shell such as Something went wrong or the privacy-extension warning:

   line 26
10. Distinctive:

    Do not ask Charlie to choose between pasting text and letting you infer.

    line 28
11. Very specific:

    Do not ask Which do you prefer?

    line 29
12. Distinctive:

    Do not present an A/B menu.

    line 30
13. Distinctive:

    Do not stop at the extraction failure.

    line 31
14. Very specific:

    Use whatever evidence you already have: tweet text, article fields from x_tweet_fetch, link title, snippet, author, visible metadata, …

    line 36
15. Distinctive:

    If the user asks for an article, post, thread, or draft:

    line 42
16. Distinctive:

    Write the deliverable immediately.

    line 44
17. Distinctive:

    Treat the source as learning material, not a reason to pause the workflow.

    line 45
18. Very specific:

    If the user says learn from it, write a new original piece instead of a summary unless they explicitly ask for a summary.

    line 46
19. Distinctive:

    Do not copy source wording or source structure unless the user explicitly asks for preservation.

    line 47
20. Distinctive:

    When evidence is partial, write the piece with honest confidence: keep claims tight, avoid fabricated specifics, and make any inference …

    line 48
21. Distinctive:

    no option menu unless Charlie explicitly asks for alternatives

    line 67

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