agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/agent-app-ingestion/.github/skills/ingestion-validation/SKILL.md

ingestion-validation

Skill188 starsChanged 13 days agoMITView on GitHub

Selects and runs evidence-based validation for Python ingestion, chunking, jobs, Azure AI Search contracts, deployment assets, and the operator frontend. Use whenever repository behavior or engineering assets change.

  • Installs packages

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. Azure/gpt-rag-ingestion★ 188100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Start with the narrowest existing command that covers the change.

    line 8
  2. Distinctive:

    Run focused tests first:

    line 19
  3. Distinctive:

    Do not require live Azure credentials for unit tests.

    line 31
  4. Distinctive:

    Verify the terminal job result and expected Azure AI Search documents, fields, ACL metadata, and deletion behavior.

    line 52
  5. Distinctive:

    If a command is unavailable or live validation is unsafe, report the missing dependency and residual risk.

    line 57

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

Ingestion validation

Start with the narrowest existing command that covers the change.

Engineering-agent assets

python -m pip install --requirement .github/scripts/requirements.txt
python .github/scripts/validate-agentic-assets.py

Python

Run focused tests first:

python -m pytest tests/<affected_test>.py

Then run the maintained suite when risk or repository policy requires it:

python -m pytest

Do not require live Azure credentials for unit tests. Reuse existing fakes, stubs, and golden fixtures.

Frontend

From frontend/, use the scripts defined in package.json:

npm test
npm run lint
npm run build

Runtime integration

For changes to formats, sources, jobs, embedding, Search payloads, or deployment:

  1. Build and run the existing container or use the applicable scripts/deploy.ps1 or scripts/deploy.sh path.
  2. Exercise a representative source and document.
  3. Verify the terminal job result and expected Azure AI Search documents, fields, ACL metadata, and deletion behavior.
  4. Inspect logs and correlated audit events without copying document content, credentials, or private environment names into public artifacts.

If a command is unavailable or live validation is unsafe, report the missing dependency and residual risk. Do not substitute an unrelated passing check.

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