agentleFS
Zengxiansheng007Zengxiansheng007/skills-old/skills/rag-downstream-handoff/SKILL.md

rag-downstream-handoff

Skill1 starsChanged 3 months agoMITView on GitHub

Use when preparing read-only D:/RAG packets for auto-testcase-generator, ui-test, Solution D, or another downstream agent without executing those downstream workflows.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Write a handoff artifact under D:/RAG/07_handover or return a read-only packet.

    line 20

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

Rag Downstream Handoff

Operating Rules

  • Produce packets only; do not run downstream tests or generators.
  • Formal downstream packets require confirmed_active RC.
  • Candidate packets must carry need-review, candidate, or blocked status.
  • Visual evidence alone is insufficient for confirmed Solution D evidence.

Workflow

  1. Identify the target: auto-testcase-generator, ui-test, Solution D, or generic agent.
  2. Load eligible Evidence Packet, RC Packet, Change Impact Packet, Test Asset Manifest, or Solution D Evidence Contract.
  3. Enforce status rules and include blocked reasons.
  4. Write a handoff artifact under D:/RAG/07_handover or return a read-only packet.

Validation

Run python D:\RAG\scripts\validate_rag_mvp.py.

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.