Airweave
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with…
Install Rfp Response Extraction
$ npx skills add pnp/sharepoint-skills --skill rfp-response-extraction -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-extraction --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/pnp/sharepoint-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .claude/skills/rfp-response-extraction && 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 "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .claude/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extractionType 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 pnp/sharepoint-skills --skill rfp-response-extraction -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-extraction --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .agents/skills/rfp-response-extraction && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .agents/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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 pnp/sharepoint-skills --skill rfp-response-extraction -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-extraction --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .cursor/skills/rfp-response-extraction && 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 "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .cursor/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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/pnp/sharepoint-skills.git --path Skills/rfp-response-extraction/rfp-response-extraction--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 pnp/sharepoint-skills --skill rfp-response-extraction -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-extraction --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .gemini/skills/rfp-response-extraction && 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 "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .gemini/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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 pnp/sharepoint-skills rfp-response-extractionInstalls 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 pnp/sharepoint-skills --skill rfp-response-extraction -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .github/skills/rfp-response-extraction && 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 "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .github/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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 pnp/sharepoint-skills --skill rfp-response-extraction -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-extraction --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Skills/rfp-response-extraction/rfp-response-extraction .opencode/skills/rfp-response-extraction && 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 "rfp-response-extraction" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-extraction/rfp-response-extraction into .opencode/skills/rfp-response-extraction/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-extraction", 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
rfp-response-extraction- GitHub stars
- 132
- Token cost
- ~1.8k tokens
- SKILL.md length
- 852 words
- Files
- 1
- Skills in repo
- 51
- Repo updated
- First seen
- Licence
- MIT
At a glance
Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with…
- Works in 5 steps: Read the RFP Document → Extract RFP Items → De-duplicate and Normalize → …
- Tasks that involve Proposals and quotes
- SKILL.md covers Firm Profile (REQUIRED — fill…, Purpose, Prerequisites and Step 1 — Read the RFP Document, plus 6 more sections
- Reaches contoso.sharepoint.com
What it does
Rfp Response Extraction is an agent skill from pnp/sharepoint-skills. Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with each item categorized, flagged for mandatory status, source-traced, and ready for owner assignment and tracking. Handles addenda by letting later versions override earlier ones.
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 Sales & Support, covering Proposals and quotes and Cloud office suites. It works with Microsoft SharePoint. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.
When your agent uses it
- Tasks that involve Proposals and quotes
- Tasks that involve Cloud office suites
Example prompts
- “Use the rfp-response-extraction skill to extract questions, mandatory requirements, submission rules, evaluation criteria, and administrative…”
- “/rfp-response-extraction”
Workflow steps
5 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 aa9eb14. 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
Hosts in commands or code, which the agent is likely to contact:
contoso.sharepoint.com
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
Rfp Response Extraction loads about 1.8k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 852 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 pnp/sharepoint-skills at commit aa9eb14, republished under its MIT licence (© pnp). 852 words, ~1,810 tokens.
Download SKILL.mdSave it as
.claude/skills/rfp-response-extraction/SKILL.md (or your agent's skills folder).- name
- rfp-response-extraction
- description
- Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with each item categorized, flagged for mandatory status, source-traced, and ready for owner assignment and tracking. Handles addenda by letting later versions override earlier ones.
RFP Extraction Skill
Firm Profile (REQUIRED — fill in before use)
These values define who your firm is and how it writes. See SETUP.md.
- FIRM NAME: [FIRM NAME]
- WHAT THE FIRM DOES: [one sentence]
- ROLE BOUNDARY: [what the firm will NOT claim to do — leave blank if none]
- VENDOR STANCE: [vendor-neutral OR resells/implements specific products]
- SPECIALIZATION: [domains the firm credibly claims]
- VOICE: [3–5 adjectives]
Purpose
Parse an RFP stored in SharePoint and populate a structured RFP Tracker List with every actionable item, each broken out by category, flagged mandatory or not, traced to its source location, and given tracking columns for owner assignment and progress monitoring.
Prerequisites
- The RFP document (PDF, Word, etc.) must be accessible in SharePoint.
- The agent must have permission to create Lists and List items in the target site.
- If the package includes addenda, attachments, or a referenced Q&A document, those should also be accessible. Flag any that are missing in the summary.
Step 1 — Read the RFP Document
- Locate the RFP file in SharePoint using the path/URL provided. If the package has multiple documents (RFP body, SOW, attachments, addenda, Q&A), list every one and capture filename, page count, and document type.
- Extract the full text of each document.
- If a document is long, process it in sections but treat it as one document for extraction.
- Process addenda last and let them override. If an addendum changes a due date, page limit, or requirement, the later version wins. Diff the changed section against the original — do not assume addenda are purely additive.
Step 1b — (Optional) Capture Solicitation Metadata
Optionally capture solicitation-level facts to an RFP Metadata list (one record per RFP). Skip for simple RFPs unless the user asks.
| Field | Where to look |
|---|---|
| RFP / reference number | Cover page or header |
| Issuing organization | Cover page |
| Primary contact + email + phone | Instructions to bidders section |
| Submission deadline (date + time + zone) | Instructions section — check addenda |
| Question / clarification deadline | Instructions section |
| Page limits | Instructions / format section |
| Font / margin / spacing rules | Format section |
| File format and naming convention | Submission instructions |
| Submission method (portal, email) | Submission instructions |
| Period of performance / contract term | Scope or terms section |
| Anticipated award / decision date | Timeline or evaluation section |
| Evaluation approach | Evaluation section (lowest price, best value, weighted scoring, etc.) |
If a field is missing, write NOT SPECIFIED and flag it in the summary so the
team can raise a clarifying question before the question deadline.
Step 2 — Extract RFP Items
Extract every item falling into a category below; record the fields listed.
Categories and What to Look For
| Category | What to Extract |
|---|---|
| Question | Any question the RFP poses (e.g., "Describe your approach to…", "How does your solution handle…") |
| Mandatory Requirement | Statements using must, shall, required, mandatory, will be required to |
| Submission Rule | How the proposal must be submitted (format, page limits, deadlines, file types, copies, labeling, volume structure) |
| Evaluation Criterion | Criteria, scoring weights, or factors used to evaluate proposals (e.g., "Price will account for 30% of the score") |
| Administrative Certification (optional 5th — use when present) | Representations & certifications, conflict-of-interest declarations, signatory authority, insurance/registration attestations, and similar pass/fail eligibility items |
Show full SKILL.md (338 more words)Show less
Fields to Record Per Item (write to the RFP Tracker list)
| Field | Value |
|---|---|
| Item | The requirement, question, or criterion text (verbatim or lightly trimmed) |
| Category | One of the five categories above |
| Mandatory | Yes / No — Yes for anything using obligatory language or marked required |
| Source Location | Page and/or section number in the source document |
| Owner | (blank — assigned later by the team) |
| Status | Not Started (default) |
Step 3 — De-duplicate and Normalize
- RFPs often restate the same requirement in multiple places. Merge obvious duplicates into one row, but keep both source locations in Source Location.
- Split compound items — a sentence asking two distinct questions becomes two rows so each can be owned and answered separately.
- Normalize phrasing for readability without changing meaning, but keep enough original wording that the row stays traceable to the document.
Step 4 — Write to the RFP Tracker List
- Create the RFP Tracker list items (or update existing ones on a re-run).
- Place Mandatory = Yes rows at the top of the sort order if the view supports it.
- Do not populate Available Content or Source columns — those are filled by the Content Finder skill in the next step of Phase 1.
Step 5 — Report Back to the User
Provide a summary with:
- Total items extracted, split by category.
- Count of mandatory vs. non-mandatory items.
- Any solicitation metadata marked
NOT SPECIFIED(if Step 1b ran). - Any referenced attachments or addenda that could not be located.
- Any ambiguous items that may need human classification.
- Confirmation that the RFP Tracker list is populated, with a link to it.
Example Summary Output
RFP Extraction complete — RFP Tracker populated.
Items extracted: 31
• Questions: 18
• Mandatory Requirements: 7
• Submission Rules: 4
• Evaluation Criteria: 2
• Administrative Certs: 0
Mandatory items: 9 (flagged and sorted to top)
Addenda processed: 1 (Addendum 2 moved the deadline +1 week — applied)
Items needing human classification: 2
• Row 14 — compound item split into two questions
• Row 22 — unclear whether procedural or content rule
RFP Tracker:
https://contoso.sharepoint.com/sites/Proposals/Lists/RFPTracker
Next step: Run the Content Finder skill to match existing content to each row.Notes & Edge Cases
- Scanned / image-only RFPs: OCR first. Flag pages with low OCR confidence.
- Conflicting addenda: The latest one wins. Note the conflict in the summary.
- No evaluation criteria stated: Record this explicitly — the Strategy Synthesis skill needs to know weights are unstated so it can infer them.
- Very large packages: Extract from each document but write to a single tracker. Keep the source filename in Source Location so every row is traceable.
© pnp, MIT. 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 Skills/rfp-response-extraction/rfp-response-extraction of pnp/sharepoint-skills.
Open the folder on GitHubat commit aa9eb14
Compare with similar skills
Rfp Response Extraction 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 |
|---|---|---|---|---|---|---|
| Rfp Response Extraction this skillpnp/sharepoint-skills | 132 | — | ~1.8k | Automated safety check: Pass | MIT | |
| AirweaveCraftOS-dev/CraftBot | 392 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 41 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Onboarding Proposalhoangnb24/repository-harness | 1.2k | — | ~4k | Automated safety check: Pass | MIT | |
| No Negative EchoLB623/no-negative-echo | 897 | — | ~965 | Automated safety check: Pass | MIT | |
| GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude | 11k | — | ~3k | Automated safety check: Notes | MIT |
Similar skills
- Official
Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Audit Onboarding Proposal
hoangnb24/repository-harness
Use only when the user explicitly invokes $audit-onboarding-proposal.
No Negative Echo
LB623/no-negative-echo
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.
GEO Service Proposal Generator
zubair-trabzada/geo-seo-claude
Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.
Architectural Proposals
FritzAndFriends/SharpSite
How to write comprehensive architectural proposals that drive alignment before code is written
More from pnp/sharepoint-skills
All 51 skills in this repoScorecard 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…
Analyze Document Library
pnp/sharepoint-skills
Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.
Broken Link Auditor
pnp/sharepoint-skills
Audits SharePoint pages, news posts, and hyperlink fields for broken or risky links and saves a self-contained HTML link-health report to the site.
Custom Image Tagger
pnp/sharepoint-skills
Analyze selected construction images, create missing object metadata columns, and write concise visual metadata back to SharePoint columns using explicit image-analysis, list-schema, list-update…
Dossier
pnp/sharepoint-skills
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.
Exec Report
pnp/sharepoint-skills
Generates a polished, self-contained HTML executive report or dashboard from any data source — SharePoint lists, CSV exports, or a user description.
Related
Works with
Categories
Questions about Rfp Response Extraction
What does Rfp Response Extraction do?
Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with…. Rfp Response Extraction is an agent skill from pnp/sharepoint-skills. Extracts questions, mandatory requirements, submission rules, evaluation criteria, and administrative certifications from a Request for Proposal (RFP) document and populates a SharePoint List with each item categorized, flagged for mandatory status, source-traced, and ready for owner assignment and tracking.
When should I use Rfp Response Extraction?
Rfp Response Extraction fits situations like: tasks that involve Proposals and quotes; tasks that involve Cloud office suites.
How do I install Rfp Response Extraction in Claude Code?
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-extraction -a claude-code`. Or copy the skill folder (Skills/rfp-response-extraction/rfp-response-extraction in pnp/sharepoint-skills) into .claude/skills/rfp-response-extraction in your project. Claude Code loads it when a task matches its description.
How do I install Rfp Response Extraction in Codex?
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-extraction -a codex`. Or copy the skill folder (Skills/rfp-response-extraction/rfp-response-extraction in pnp/sharepoint-skills) into .agents/skills/rfp-response-extraction in your project. Codex loads it when a task matches its description.
Can I use Rfp Response Extraction 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 pnp/sharepoint-skills --skill rfp-response-extraction -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rfp-response-extraction, .gemini/skills/rfp-response-extraction, .github/skills/rfp-response-extraction and .opencode/skills/rfp-response-extraction in your project.
What does Rfp Response Extraction need to run?
SKILL.md names no scripts, command-line tools or credentials: Rfp Response Extraction is instructions for the agent only.
Does Rfp Response Extraction access the network?
SKILL.md names 1 domain. In commands or code: contoso.sharepoint.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Rfp Response Extraction 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 Rfp Response Extraction use?
Rfp Response Extraction is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Rfp Response Extraction use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Rfp Response Extraction?
Skills that share tags, products or a category with Rfp Response Extraction: Airweave (CraftOS-dev/CraftBot, 392 stars), Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars) and No Negative Echo (LB623/no-negative-echo, 897 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rfp Response Extraction?
pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 132 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 6, 2026.
Source: pnp/sharepoint-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.