procurement-audit
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度). Use for 采购审核, contract compliance checklists, or procurement statistics rollups.
npx skills add vixues/LeAgent --skill procurement-audit --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Procurement audit ## Scope Map each claim/contract clause to an explicit rule in the uploaded policy pack. Do not invent institutional thresholds. ## Before starting Call **`ask_user` alone** when needed for: - Which rule documents apply - Audit depth (full checklist vs spot-check) - Whether to produce a summary stats sheet plus a findings sheet ## Multi-file join When ≥2 attachments are present (catalog, contract, bid sheet): 1. List each file’s role and key columns 2. Align join keys before filling any template 3. Flag unmatched rows explicitly ## Output - Findings table with rule citation + evidence snippet - Optional stats rollup Excel - Always return managed `file_id` / `download_url` When the user adds a missed rule (e.g. lodging-equivalent procurement caps), update this skill / procedure for subsequent runs.
- Scope
- Before starting
- Multi-file join
- Output
What does the procurement-audit skill do?
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度). Use for 采购审核, contract compliance checklists, or procurement statistics rollups.
How do I install it?
Run `npx skills add vixues/LeAgent --skill procurement-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vixues/LeAgent, a repository with 195 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.