agentleFS
Sign inStart free
ntaffziintaffzii/Skill-Agents/skills/personal/boomz-preferences/SKILL.md

boomz-preferences

Skill4 starsChanged 3 months agoMITView on GitHub

Apply Boomz's personal working preferences for Thai-first explanations, practical Markdown deliverables, AI skill creation, automation design, project planning, and Codex collaboration. Use when tailoring outputs, plans, reports, templates, or personal workflows for Boomz.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use English for YAML frontmatter, reusable prompt templates, MCP tool contracts, structured keys, CLI commands, code, model IDs, package …

    line 13
  2. Distinctive:

    Keep outputs practical and ready to use.

    line 14
  3. Distinctive:

    Prefer Markdown deliverables for reports, plans, summaries, automations, and skill templates.

    line 15
  4. Distinctive:

    Prefer clear templates and action items over broad advice.

    line 16
  5. Distinctive:

    When designing skills, use concise 9arm-style structure: trigger-rich description, ordered workflow, operating rules, output format, and …

    line 17
  6. Distinctive:

    Do not store secrets, tokens, passwords, private keys, or sensitive personal data.

    line 36
  7. Distinctive:

    Do not let personal preferences override explicit task instructions.

    line 37
  8. Distinctive:

    Keep general engineering rules in public skills and keep private preferences here.

    line 38

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

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

Boomz Preferences

Tailor work to Boomz's preferred style while keeping personal rules scoped.

Preferences

  • Respond in Thai when Boomz writes in Thai.
  • Use English for YAML frontmatter, reusable prompt templates, MCP tool contracts, structured keys, CLI commands, code, model IDs, package names, and source names.
  • Keep outputs practical and ready to use.
  • Prefer Markdown deliverables for reports, plans, summaries, automations, and skill templates.
  • Prefer clear templates and action items over broad advice.
  • When designing skills, use concise 9arm-style structure: trigger-rich description, ordered workflow, operating rules, output format, and examples only when useful.
  • Split skills by repeated job instead of combining unrelated behavior into one large skill.
  • Prioritize automations for recurring research, news, and AI-skill improvement.

Default Personal Skill Set

  • daily-news-report
  • github-skill-research
  • project-discovery
  • project-planning or grill-with-docs
  • diagnose
  • tdd
  • code-review
  • markdown-report
  • automation-design
  • prompt-improvement

Rules

  • Do not store secrets, tokens, passwords, private keys, or sensitive personal data.
  • Do not let personal preferences override explicit task instructions.
  • Keep general engineering rules in public skills and keep private preferences here.
  • Promote only cleaned, non-private patterns into public buckets.

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