agentleFS
Sign inStart free
Catherine1401Catherine1401/agent-skills/skills/be-ms/SKILL.md

be-ms

Skill2 starsChanged 54 days agoMITView on GitHub

Draft a message to send to the backend (BE) team about an issue, ready to paste into chat. Use when asked to draft, write or compose a message, question or report for BE; not for Jira comments or code changes.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Write in Vietnamese, as plain text ready to paste.

    line 6
  2. Distinctive:

    No personal pronouns or forms of address (tôi, mình, anh, chị, em, bạn, BE ơi…), no greetings, thanks or sign-off.

    line 7
  3. Distinctive:

    Read the app's current mappers and data sources first.

    line 10

≈ “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
  • Write in Vietnamese, as plain text ready to paste; deliver it in the reply, never send it anywhere.
  • No personal pronouns or forms of address (tôi, mình, anh, chị, em, bạn, BE ơi…), no greetings, thanks or sign-off; use impersonal sentences that state the issue.
  • Structure: bold title (ticket key if known) → Hiện trạng: one line observed + one line requested → numbered sections per endpoint, each with Request: and Response: code blocks (method + full path, complete JSON with realistic values) → Cần BE xác nhận only for points the app cannot decide; omit any empty part.
  • The app owns field names, enum values and payload shape: state them as requirements; never ask BE to confirm or choose them.
  • Read the app's current mappers and data sources first; reuse their existing field names and endpoints.
  • Omit app-internal findings, root-cause analysis, verification notes and prose explanations; one fact per line.
  • Mask secrets and card data (PAN → first 4 + last 4, no full tokens, passwords or CVV values).

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