agentleFS
Sign inStart free
wublinuxwublinux/supply-chain-local-agent/skills/supply-chain-qa/SKILL.md

supply-chain-qa

Skill0 starsChanged 3 months agoMITView on GitHub

Use when answering questions about local company policies, agreements, SOPs, transport processes, diagrams, or operational notes through the supply-chain knowledge base.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call kb_search before making any company-specific claim.

    line 8
  2. Very specific:

    Use kb_get when the returned excerpt is insufficient or the exact wording matters.

    line 9
  3. Distinctive:

    Never use a draft company policy or framework agreement as the basis of a conclusion.

    line 12
  4. Distinctive:

    Treat extracted contact names as candidates unless the contact record is explicitly confirmed.

    line 13
  5. Distinctive:

    If sources conflict, present both versions and their effective dates instead of choosing silently.

    line 14

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

Supply Chain Knowledge Q&A

  1. Call kb_search before making any company-specific claim.
  2. Use kb_get when the returned excerpt is insufficient or the exact wording matters.
  3. Cite every substantive conclusion with its exact source locator: [来源: 文件名, 第N页/幻灯片N/工作表!A1:H20].
  4. Clearly label draft sources as 未审核.
  5. Never use a draft company policy or framework agreement as the basis of a conclusion. Ask for review or say that the knowledge base has no reliable basis.
  6. Treat extracted contact names as candidates unless the contact record is explicitly confirmed.
  7. If sources conflict, present both versions and their effective dates instead of choosing silently.
  8. Agreement retrieval is informational and is not legal advice.

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