We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

• ≈0

  Common · estimate

  Many files like this have a rule of this kind.

• ≈2

  Distinctive · estimate

  This author's own choices. Worth a look.

• 6

  Very specific

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

• Common
• Distinctive
• Very specific

1. Very specific:

   Use this skill when a user asks for proof, screenshots, page evidence, a before and after capture, or a reproducible record of a browser …

   line 15
2. Very specific:

   Call get_page_snapshot to capture URL, title, and visible text.

   line 26
3. Very specific:

   Call take_screenshot with a sanitized label.

   line 27
4. Very specific:

   If a specific UI element matters, capture a second screenshot with selector.

   line 29
5. Very specific:

   Call list_artifacts and record the new screenshot file names.

   line 31
6. Distinctive:

   Never include passwords, auth tokens, cookies, or raw headers in summaries.

   line 37
7. Distinctive:

   Never persist credentials in artifacts.

   line 38
8. Very specific:

   Never bypass take_screenshot or file tools with ad hoc filesystem paths.

   line 39

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