agentleFS
Sign inStart free
pymc-labspymc-labs/pymc-marketing/.agents/skills/docs/SKILL.md

docs

Skill1.3k starsChanged 31 days agoApache-2.0View on GitHub

Use whenever creating or editing PyMC-Marketing documentation, including small updates to existing notebooks. Apply the repository's documentation conventions and notebook visibility policy.

169 other projects use a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 3 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 4 mentionsJul 2026: 4 mentionsAug 2026: 2 mentionsSep 2026: 3 mentionsOct 2026: 2 mentionsNov 2026: 3 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the pymc-labs/pymc-marketing repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about pymc-labs/pymc-marketing

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Bluesky (51 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 1

Used with

Projects with it also use import-memory, perf and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • amirbironSkill

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 3 projects that use this

  • MicrosoftSkill

    perf

    Speed and memory performance rules for Rust crates, the Node addon, webui-framework, and webui-delivery.

    Also in 4 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 3 projects that use this

  • JkudjoSkill

    incident

    Production incident response — structured triage, hypothesis tree, safe remediation, incident record

    Also in 4 projects that use this

  • vbrevikSkill

    work

    Use when the user says 'plan', 'todo', 'copy plan', 'append plan', 'resume plan', 'priorities', or 'what's next'.

    Also in 7 projects that use this

  • mbwsimsSkill

    impact

    This skill should be used when the user asks to "check the impact", "what will break if I change this", "blast radius", "impact analysis", "what depends on this", "who imports this", "is it safe to change this", mentions "/impact", or wants to understand the consequences of modifying a specific file or function before making changes.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 133 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When delegating documentation work, include this skill's path in the worker's task.

    line 8
  2. Very specific:

    Use hide-input for incidental plotting, formatting, and data manipulation, unless those operations are being taught.

    line 15
  3. Very specific:

    Use hide-output for trivial output, including MCMC messages and progress displays, unless sampler behavior is part of the argument.

    line 16
  4. Distinctive:

    Keep explanatory figures, comparisons, relevant diagnostics, and consequential warnings or unexpected results visible.

    line 17
  5. Very specific:

    Add tags to cell.metadata.tags, preserving existing tags, code, and stored outputs.

    line 20
  6. Distinctive:

    Check the rendered page when practical.

    line 21

“Common” is measured: kept by at least 6 in 10 of the 133 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Docs

When delegating documentation work, include this skill's path in the worker's task.

Notebook visibility

For every new or edited documentation notebook, review visibility throughout the notebook:

  • Show code central to the teaching arc, such as model definitions, key API calls, and essential analysis.
  • Use hide-input for incidental plotting, formatting, and data manipulation, unless those operations are being taught.
  • Use hide-output for trivial output, including MCMC messages and progress displays, unless sampler behavior is part of the argument.
  • Keep explanatory figures, comparisons, relevant diagnostics, and consequential warnings or unexpected results visible.
  • Choose input and output visibility independently; split mixed-purpose cells when necessary.

Add tags to cell.metadata.tags, preserving existing tags, code, and stored outputs. Check the rendered page when practical. For visibility-only edits, validate notebook structure and confirm code and results are unchanged; resampling is unnecessary.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free