Serenity Alpha
haskaomni/serenity-skill
Translate market-moving news into investable alpha hypotheses by mapping observed demand changes to revenue lines, supply chains, small-cap financial elasticity, market misclassification, validation…
A procurement document set generation pipeline. An agent skill from revfactory/harness-100.
Install Procurement Docs
$ npx skills add revfactory/harness-100 --skill procurement-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 procurement-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .claude/skills/procurement-docs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .claude/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add revfactory/harness-100 --skill procurement-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 procurement-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .agents/skills/procurement-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .agents/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill procurement-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 procurement-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .cursor/skills/procurement-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .cursor/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/revfactory/harness-100.git --path en/95-procurement-docs/.claude/skills/procurement-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add revfactory/harness-100 --skill procurement-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 procurement-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .gemini/skills/procurement-docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .gemini/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install revfactory/harness-100 procurement-docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add revfactory/harness-100 --skill procurement-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .github/skills/procurement-docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .github/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add revfactory/harness-100 --skill procurement-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 procurement-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/95-procurement-docs/.claude/skills/procurement-docs .opencode/skills/procurement-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "procurement-docs" agent skill from https://github.com/revfactory/harness-100/tree/main/en/95-procurement-docs/.claude/skills/procurement-docs into .opencode/skills/procurement-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "procurement-docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
procurement-docs- GitHub stars
- 1.3k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 664 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A procurement document set generation pipeline. An agent skill from revfactory/harness-100.
- Works in 3 steps: Preparation (performed directly by the… → Team Assembly and Execution → Integration and Final Deliverables
- Create procurement documents
- SKILL.md covers Execution Mode, Agent Roster, Workflow and Execution Modes by Scope, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Procurement Docs is an agent skill from revfactory/harness-100. A procurement document set generation pipeline. An agent team collaborates to produce requirements definitions, vendor comparisons, evaluation criteria, contract terms, and acceptance criteria. Use this skill for 'create procurement documents', 'vendor comparison', 'procurement specifications', 'evaluation criteria', 'acceptance criteria', 'procurement documents', 'bid evaluation', 'RFP creation', 'vendor selection', and similar procurement/sourcing document topics. Actual ordering, contract execution, payment…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Vendor and procurement management. The licence is Apache-2.0.
When your agent uses it
- Create procurement documents
- Vendor comparison
- Procurement specifications
- Evaluation criteria
Example prompts
- “create procurement documents”
- “vendor comparison”
- “procurement specifications”
- “/procurement-docs”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Procurement Docs loads about 1.8k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 664 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 664 words, ~1,818 tokens.
Download SKILL.mdSave it as
.claude/skills/procurement-docs/SKILL.md (or your agent's skills folder).- name
- procurement-docs
- description
- A procurement document set generation pipeline. An agent team collaborates to produce requirements definitions, vendor comparisons, evaluation criteria, contract terms, and acceptance criteria. Use this skill for 'create procurement documents', 'vendor comparison', 'procurement specifications', 'evaluation criteria', 'acceptance criteria', 'procurement documents', 'bid evaluation', 'RFP creation', 'vendor selection', and similar procurement/sourcing document topics. Actual ordering, contract execution, payment processing, and asset registration are out of scope.
Procurement Docs — Procurement Document Set Generation Pipeline
Generates procurement requirements, vendor comparisons, evaluation criteria, contract term reviews, and acceptance criteria through agent team collaboration.
Execution Mode
Agent Team — 5 members communicate directly via SendMessage and cross-validate each other's work.
Agent Roster
| Agent | File | Role | Type |
|---|---|---|---|
| requirements-definer | .claude/agents/requirements-definer.md | Specifications, quantity, delivery, budget | general-purpose |
| vendor-comparator | .claude/agents/vendor-comparator.md | Candidate research, comparison tables, SWOT | general-purpose |
| evaluation-designer | .claude/agents/evaluation-designer.md | Scoring, weighting, evaluation process | general-purpose |
| contract-reviewer | .claude/agents/contract-reviewer.md | Clauses, risks, SLA, negotiation | general-purpose |
| acceptance-builder | .claude/agents/acceptance-builder.md | Inspection items, testing, pass criteria | general-purpose |
Workflow
Phase 1: Preparation (performed directly by the orchestrator)
- Extract from user input:
- Procurement target: Goods, software, services, construction, etc.
- Procurement context: New introduction, replacement, expansion, etc.
- Budget: Budget range or limit
- Timeline: Desired delivery date, project schedule
- Vendor candidates (optional): Vendors already under consideration
- Existing documents (optional): Existing specifications, contract drafts
- Create the
_workspace/directory in the project root - Organize the input and save to
_workspace/00_input.md - Determine the execution mode based on the request scope
Phase 2: Team Assembly and Execution
| Order | Task | Owner | Dependencies | Deliverable |
|---|---|---|---|---|
| 1 | Requirements definition | definer | None | _workspace/01_requirements_spec.md |
| 2 | Vendor comparison | comparator | Task 1 | _workspace/02_vendor_comparison.md |
| 3a | Evaluation criteria | evaluator | Tasks 1, 2 | _workspace/03_evaluation_criteria.md |
| 3b | Contract review | contract | Tasks 1, 2 | _workspace/04_contract_review.md |
| 4 | Acceptance criteria | acceptance | Tasks 1, 3b | _workspace/05_acceptance_criteria.md |
Tasks 3a (evaluation) and 3b (contract) run in parallel.
Inter-team communication flow:
- definer completes → sends requirements/budget to comparator, priorities/criteria to evaluator, delivery/support terms to contract, must-have requirements/criteria to acceptance
- comparator completes → sends vendor info/comparison items to evaluator, license/clause highlights to contract
- contract completes → sends acceptance conditions/warranty to acceptance
- Orchestrator performs final cross-document consistency validation
Phase 3: Integration and Final Deliverables
- Verify all files in
_workspace/ - Cross-validation:
- All must-have requirements are reflected in acceptance criteria
- Evaluation criteria weight totals equal 100%
- Contract terms align with requirements/acceptance criteria
- Vendor comparison items map to requirements
- Generate procurement summary report at
_workspace/06_procurement_summary.md - Report the final summary to the user
Execution Modes by Scope
| User Request Pattern | Execution Mode | Agents Involved |
|---|---|---|
| "Create complete procurement documents" | Full Pipeline | All 5 |
| "Just write the requirements spec" | Spec Mode | definer solo |
| "Just compare vendors" | Comparison Mode | definer + comparator |
| "Just create evaluation criteria" | Evaluation Mode | definer + evaluator |
| "Review this contract" | Review Mode | contract solo |
| "Just create acceptance criteria" | Acceptance Mode | definer + acceptance |
Data Transfer Protocol
| Strategy | Method | Usage |
|---|---|---|
| File-based | _workspace/ directory | Primary deliverable storage and sharing |
| Message-based | SendMessage | Real-time key information transfer, correction requests |
| Task-based | TaskCreate/TaskUpdate | Progress tracking, dependency management |
Show full SKILL.md (259 more words)Show less
Error Handling
| Error Type | Strategy |
|---|---|
| Unclear procurement target | definer presents clarifying question list, works from answers |
| Insufficient vendor info | comparator provides RFI template when web search fails, requests user direct input |
| Budget undetermined | Estimate budget range based on market prices, proceed after user confirmation |
| Legal review needed | contract tags with "[Legal review needed]", warns cannot replace legal counsel |
| Agent failure | 1 retry → proceed without that deliverable if still failing, note in report |
Test Scenarios
Normal Flow
Prompt: "Create a procurement document set for cloud server hosting services. Budget is $500K/year and I want to compare AWS, Azure, and GCP." Expected Results:
- Spec: Compute/storage/network requirements, SLA requirements
- Comparison: 3-provider feature/price/support comparison, TCO analysis, SWOT
- Evaluation: Technical 40% / Price 30% / Support 20% / Reliability 10% scoring
- Contract: SLA clauses, data sovereignty, termination terms, negotiation points
- Acceptance: Infrastructure deployment acceptance, performance testing, SLA compliance verification
Existing File Flow
Prompt: "I already have a spec. Just create vendor comparison and evaluation criteria." + spec file Expected Results:
- Existing spec copied to
_workspace/01_requirements_spec.md - Comparison + evaluation mode: comparator + evaluator deployed
- Vendor comparison and evaluation criteria generated from spec
Error Flow
Prompt: "I need to buy something but don't know what, maybe work laptops?" Expected Results:
- definer presents clarifying questions (use case, number of users, performance needs, etc.)
- Requirements derived from user responses
- Market price range presented if budget is undetermined
- Report notes "Requirements confirmation needed"
Agent Extension Skills
| Extension Skill | Path | Target Agent | Role |
|---|---|---|---|
| vendor-scoring | .claude/skills/vendor-scoring/skill.md | vendor-comparator, evaluation-designer | Vendor evaluation scorecard, pricing formulas, reference checks |
| contract-checklist | .claude/skills/contract-checklist/skill.md | contract-reviewer, acceptance-builder | Contract 10 key clauses, SLA design, acceptance criteria |
© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/95-procurement-docs/.claude/skills/procurement-docs of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Procurement Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Procurement Docs this skillrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Serenity Alphahaskaomni/serenity-skill | 632 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Scorecard Matrixpnp/sharepoint-skills | 131 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Buyer Job Intent Analysiselvisun/newsjack | 1.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Energy Procurementaffaan-m/ECC | 274k | 4 repos | ~7.4k | Automated safety check: Pass | Apache-2.0 | |
| Master Builderibuilder/massing | 121 | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Scorecard Matrix
pnp/sharepoint-skills
Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a…
Buyer Job Intent Analysis
elvisun/newsjack
Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language.
Energy Procurement
affaan-m/ECC
Procure electricity and natural gas for commercial and industrial facilities: tariff and rate-schedule optimization, demand-charge mitigation, supplier RFPs, fixed/index/block-and-index hedging…
Master Builder
ibuilder/massing
Reason like a master builder — one mind holding an entire built-asset project from raw land through design, construction, handover, operations, and disposition, anywhere in the world.
Procurement Audit
vixues/LeAgent
Review procurement contracts and purchase packages against uploaded compliance rules (招标/采购制度).
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Procurement Docs
What does Procurement Docs do?
A procurement document set generation pipeline. An agent skill from revfactory/harness-100. Procurement Docs is an agent skill from revfactory/harness-100. A procurement document set generation pipeline.
When should I use Procurement Docs?
Procurement Docs fits situations like: create procurement documents; vendor comparison; procurement specifications; evaluation criteria.
How do I install Procurement Docs in Claude Code?
Run `npx skills add revfactory/harness-100 --skill procurement-docs -a claude-code`. Or copy the skill folder (en/95-procurement-docs/.claude/skills/procurement-docs in revfactory/harness-100) into .claude/skills/procurement-docs in your project. Claude Code loads it when a task matches its description.
How do I install Procurement Docs in Codex?
Run `npx skills add revfactory/harness-100 --skill procurement-docs -a codex`. Or copy the skill folder (en/95-procurement-docs/.claude/skills/procurement-docs in revfactory/harness-100) into .agents/skills/procurement-docs in your project. Codex loads it when a task matches its description.
Can I use Procurement Docs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add revfactory/harness-100 --skill procurement-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/procurement-docs, .gemini/skills/procurement-docs, .github/skills/procurement-docs and .opencode/skills/procurement-docs in your project.
What does Procurement Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Procurement Docs is instructions for the agent only.
Does Procurement Docs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Procurement Docs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Procurement Docs use?
Procurement Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Procurement Docs use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Procurement Docs?
Skills that share tags, products or a category with Procurement Docs: Serenity Alpha (haskaomni/serenity-skill, 632 stars), Scorecard Matrix (pnp/sharepoint-skills, 131 stars), Buyer Job Intent Analysis (elvisun/newsjack, 1.5k stars) and Energy Procurement (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Procurement Docs?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,290 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.