Authoring Rfds
symposium-dev/symposium
Write and structure RFDs (Requests for Discussion) for the Symposium project.
Reads multiple input documents — past proposals, a win strategy brief, capability statements, a win/loss debrief, and RFP evaluation criteria — and synthesizes them into a recommended proposal Table…
$ npx skills add pnp/sharepoint-skills --skill rfp-response-strategy-synthesis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-strategy-synthesis --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-strategy-synthesis/rfp-response-strategy-synthesis .claude/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .claude/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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-strategy-synthesis/rfp-response-strategy-synthesisType 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-strategy-synthesis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-strategy-synthesis --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-strategy-synthesis/rfp-response-strategy-synthesis .agents/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .agents/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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-strategy-synthesis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-strategy-synthesis --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-strategy-synthesis/rfp-response-strategy-synthesis .cursor/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .cursor/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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-strategy-synthesis/rfp-response-strategy-synthesis--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-strategy-synthesis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-strategy-synthesis --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-strategy-synthesis/rfp-response-strategy-synthesis .gemini/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .gemini/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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-strategy-synthesisInstalls 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-strategy-synthesis -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-strategy-synthesis/rfp-response-strategy-synthesis .github/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .github/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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-strategy-synthesis -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-strategy-synthesis --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-strategy-synthesis/rfp-response-strategy-synthesis .opencode/skills/rfp-response-strategy-synthesis && 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-strategy-synthesis" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis into .opencode/skills/rfp-response-strategy-synthesis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-strategy-synthesis", 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.
rfp-response-strategy-synthesisReads multiple input documents — past proposals, a win strategy brief, capability statements, a win/loss debrief, and RFP evaluation criteria — and synthesizes them into a recommended proposal Table…
Rfp Response Strategy Synthesis is an agent skill from pnp/sharepoint-skills. Reads multiple input documents — past proposals, a win strategy brief, capability statements, a win/loss debrief, and RFP evaluation criteria — and synthesizes them into a recommended proposal Table of Contents and a content strategy brief. Produces an explicit competitive-positioning recommendation and a page-budget allocation table. Designed to run after content mapping (Phase 1) and before any drafting begins (Phase 3).
Its SKILL.md is about 6.9k 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 Content strategy. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 69712d2. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Rfp Response Strategy Synthesis loads about 6.9k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 2,623 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.
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.
The full file from pnp/sharepoint-skills at commit 69712d2, republished under its MIT licence (© pnp). 2,623 words, ~6,857 tokens.
.claude/skills/rfp-response-strategy-synthesis/SKILL.md (or your agent's skills folder).These values define who your firm is and how it writes. See SETUP.md.
Before any content is drafted, the proposal needs a coherent response strategy: a clear point of view on what the client cares about most, how the firm's capabilities map to those priorities, and what narrative arc is most persuasive. This skill synthesizes multiple inputs into two deliverables — a recommended Table of Contents and a Content Strategy Brief — that become the approved blueprint for Phase 3. Nothing in Phase 3 should be drafted without an approved output from this skill.
Do not output the Coverage Map, Table of Contents, or Content Strategy Brief to chat. These are document deliverables. All content from Steps 6–8 goes directly into the Word document saved in Step 9. Chat output is limited to one-line progress updates per step and the final summary.
Read each input with a specific extraction goal — know what you are looking for before you read. These extracts feed the analysis in Steps 2–4.
RFP Tracker List:
Past Proposals (2–3):
Win Strategy Brief:
Win/Loss Debrief:
Capability Statements:
The evaluation criteria reveal what the client actually scores on — analyze them first.
Using the Step 1 extracts:
Take an explicit position on how the firm should compete before writing themes — a proposal that wins on capability is structured very differently from one that wins on price. For each lever, score the firm's position as Lead with, Match competitors, or Concede:
| Lever | Lead with means… | Match means… | Concede means… |
|---|---|---|---|
| Price | We can credibly price below the likely competitive median and that is our strongest path to win. | Our price will be in band; neutralize price as a factor and shift evaluators to other dimensions. | Our price will be higher; we must justify the premium with capability or risk superiority. |
| Capability / technical strength | We have a defensible differentiator (named methodology, relevant prior experience, qualified personnel) no competitor can match. | Credible but not uniquely strong; meet every requirement cleanly. | Gaps in credentials or track record; neutralize, not win, on capability. |
| Delivery risk | We can credibly claim lower delivery risk (track record, named team commitment, transition plan, stability) than competitors. | Risk profile comparable to competitors; meet every requirement cleanly. | Visible risk (smaller firm, limited track record, dependencies); neutralize. |
Combine the three scores into a single recommendation: which lever the proposal leads with, matches, and concedes/neutralizes. This is written into the Content Strategy Brief as Section 3 (Step 8).
If the Win Strategy Brief and the RFP's evaluation approach contradict each other (e.g., salesperson says "price will win" but evaluation weights capability at 60%), flag the conflict explicitly and surface it for human decision in the Content Gaps section — do not resolve it unilaterally.
Combine the Step 2–4 analysis into strategic themes that anchor the narrative. A strategic theme ties a client priority (from evaluation criteria and Win Strategy Brief) to a firm strength (from capabilities and past proposals).
Theme: [Short label, e.g., "Proven Delivery at Scale"]
Client priority it addresses: [e.g., "Implementation track record — 25% of scoring"]
Firm differentiator: [e.g., "200+ similar engagements, 94% on-time delivery rate"]
Supporting content available: [Document names from Available Content column]
Content gaps: [Any mandatory requirements not yet covered by this theme]
Risk: [e.g., "Competitor X likely claims similar track record — need specific proof points"]Also classify:
If the Content Finder flagged any reference/past-performance row as No Match or weak match (low relevance, dated, wrong sector, wrong scale), the Content Strategy Brief must include a neutralization theme that compensates. A weak references section is one of the most common reasons proposals lose — do not skip this.
For each flagged gap, propose at least one compensating move:
Write the compensation plan into the Content Strategy Brief as Section 6, in an explicit subsection titled "Reference Gap Compensation".
Using the strategic themes and evaluation-criteria ranking as primary drivers, produce a ToC that:
RECOMMENDED TABLE OF CONTENTS
[Client / RFP Name] — [Date]
1. Executive Summary
1.1 Our Understanding of Your Needs
1.2 Our Recommended Approach
1.3 Why [Firm Name]
2. [Section tied to highest-weighted evaluation criterion]
2.1 ...
3. [Section tied to second-weighted criterion or primary strategic theme]
3.1 ...
[Continue for all major themes and mandatory requirements]
Appendix A — [e.g., Team Profiles]
Appendix B — [e.g., Case Studies]
Appendix C — [e.g., Required Forms / Certifications]For each section, add a one-line annotation explaining the strategic rationale:
"Section 2 leads because 'Implementation Experience' carries 30% of evaluation weight and is our strongest differentiator."
Allocate the total page limit (from Step 2) across ToC sections proportional to evaluation weight. A page budget gives the Phase 3 agent a hard space constraint per section and prevents low-weight sections from consuming pages that should go to high-weight ones.
PAGE BUDGET ALLOCATION
Total body limit: 25 pages
Section | Title | Evaluation Weight | Allocated Pages | Rationale
--------|------------------------------------|-------------------|-----------------|----------
1 | Executive Summary | — | 2.0 | Fixed allowance (8% of body)
2 | Technical Approach | 40% | 9.0 | Highest-weighted factor
3 | Management Approach | 20% | 4.5 | Second-weighted factor
4 | Relevant Experience | 20% | 4.5 | Body narrative; references in appendix
5 | Team & Key Personnel | 10% | 2.5 | Body narrative; résumés in Appendix A
6 | Pricing Narrative | 10% | 2.5 | Body narrative; pricing in separate section
| TOTAL | 100% | 25.0 |The Phase 3 agent treats allocated pages as a hard ceiling, not a target. Overflow goes to an appendix (if the RFP allows) or is cut — drafting outside the budget is not allowed without re-approval at the human gate.
Before finalising the ToC, cross-reference every RFP Tracker row against the proposed sections. The ToC must account for every Question, Mandatory Requirement, and content-bearing Submission Rule — no row left without a home. A compelling structure that misses a requirement is a compliance failure.
COVERAGE MAP
RFP Row | Item (abbreviated) | Category | Rule Type | ToC Section / Checklist | Notes
--------|-------------------|----------|-----------|-----------------------|------
Row 1 | Describe your transformation methodology | Question | — | Section 2 — Approach | Primary coverage
Row 2 | Provide 2 examples of relevant experience | Question | — | Section 4 + Appendix B | Examples in appendix, referenced in body
Row 3 | Bidder must have authority to contract | Mandatory | — | Appendix C — Certifications | Admin qualifier
Row 4 | 90-day execution plan | Question | — | Section 3 — Execution Plan | Standalone section added
Row 5 | Submit proposal in PDF, max 30 pages | Submission Rule | Procedural | Submission Checklist | No ToC coverage needed
Row 6 | Include signed pricing workbook | Submission Rule | Content | Appendix D — Pricing Workbook | Required appendix added
[GAP] | Describe subcontracting strategy | Mandatory | — | NOT COVERED | Add Section 6 or subsectionDo not proceed to Step 8 until the Coverage Map shows zero content gaps. Procedural rules should all appear in the Submission Checklist with no ToC mapping. If a content gap cannot be resolved without human input (e.g., SME content that doesn't exist), flag it explicitly in the Content Gaps section of the Content Strategy Brief.
A short companion document to the ToC giving the Phase 3 agent and the human reviewer a clear set of instructions for how the proposal should be written, not just what it should contain.
CONTENT STRATEGY BRIEF
[Client / RFP Name] — [Date]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. SITUATION SUMMARY
What the client is trying to achieve, based on the RFP and Win Strategy Brief.
[2–3 sentences — the agent's synthesis of what the client actually cares about,
not a restatement of the RFP]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. OUR CORE VALUE PROPOSITION FOR THIS DEAL
The single overarching message the proposal should convey. [1–2 sentences]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. COMPETITIVE POSITIONING RECOMMENDATION (from Step 4)
• Price: [Lead with / Match / Concede] — [1-sentence rationale]
• Capability: [Lead with / Match / Concede] — [1-sentence rationale]
• Delivery risk:[Lead with / Match / Concede] — [1-sentence rationale]
Overall recommendation: [1–2 sentences — which lever leads, matches, neutralizes;
what evaluator behavior this implies; any conflict with the Win Strategy Brief the
human gate must resolve]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. STRATEGIC THEMES
[3–5 themes in the Step 5 format]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. TONE AND VOICE GUIDANCE
- Overall tone: [from Firm Profile VOICE — e.g., "Confident and specific — avoid hedging"]
- Technical depth: [e.g., "Moderate — client is a business buyer, not technical"]
- Language to emphasize: [e.g., "Outcomes, track record, client-centricity"]
- Language to avoid: [e.g., "Jargon, vague superlatives, boilerplate disclaimers in body text"]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6. RISKS AND NEUTRALIZATION STRATEGY
[For each risk/weakness, a 1–2 sentence recommended handling approach]
6a. Reference Gap Compensation (required if Content Finder flagged reference gaps)
[For each flagged gap row, the chosen compensating move from Step 5 and a
1-sentence drafting instruction]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
7. CONTENT GAPS REQUIRING SME OR SALESPERSON INPUT
[RFP items with no content match and no existing capability coverage — must be
addressed by a human before Phase 3 drafting begins]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
8. PAGE BUDGET ALLOCATION
[Page Budget Table from Step 6b]
Drafting rule: allocated pages are a hard ceiling, not a target. Overflow goes to
an appendix (if the RFP allows) or is cut. No section exceeds its allocation
without re-approval at the human gate.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
9. SECTION-BY-SECTION DRAFTING NOTES
For each ToC section:
Section [X]: [Allocated pages from Section 8] — [Drafting instruction — what to
emphasize, what content to draw from, what to avoid, and where the section
reinforces the competitive positioning stance from Section 3][ClientShortName]_[RFPShortName]_[Year] (one or two meaningful words each, underscores, no spaces — e.g., Northwind_TransformationRFP_2026)Strategy Synthesis complete.
Inputs processed:
• RFP Tracker list: 31 rows analyzed (18 Questions, 7 Mandatory,
4 Evaluation Criteria, 2 Submission Rules)
• Past proposals reviewed: 3 (2 wins, 1 loss)
• Win Strategy Brief: Read and synthesized
• Capability Statements: 3 documents
• Win/Loss Debrief: Read and synthesized
Competitive positioning recommendation:
• Price: Match — bid in band, neutralize as a factor
• Capability: Lead with — named methodology + relevant prior experience
• Delivery risk: Match — strong transition plan offsets firm size
Strategic themes identified: 4
1. Governance-First Transformation (win theme)
2. Vendor-Neutral Independence (win theme)
3. Structured Knowledge Transfer (win theme)
4. 90-Day Execution Readiness (neutralization theme)
Reference gap compensation: 2 flagged rows
• Row 9 — Healthcare reference gap → cite analog engagement + name lead
with sector experience
• Row 17 — Security reference gap → lead with teaming partner reference
Page budget allocated: 25 body pages
Exec Summary 2.0 • Technical 9.0 • Management 4.5
Experience 4.5 • Team 2.5 • Pricing 2.5
Coverage Map: 31 rows mapped
Fully covered: 27 rows
Coverage gaps resolved: 2 rows (new subsections added to ToC)
Appendix items confirmed: 2 (Certifications, Pricing Workbook)
Submission rules classified: 4 total
• Procedural (Submission Checklist): 2 (page limit, file format)
• Content (ToC/Appendix): 2 (signed pricing workbook, staffing plan)
Content gaps requiring human input before Phase 3 (5 items):
• Row 9 — Examples of engagements in a healthcare context (none in library)
• Row 14 — Subcontracting strategy (firm policy input needed)
• Row 19 — Data residency controls (SME required)
• Row 26 — Pricing model and rate card (salesperson must provide)
• Row 30 — Innovation roadmap (no existing content)
Deal workspace:
WIP Collaboration Folder / Northwind_TransformationRFP_2026 /
Strategy Brief (Word document):
Northwind_Strategy_Brief_2026-03-03.docx
[ SharePoint link or download link ]
Next steps: Salesperson and pursuit lead to open the Strategy Brief, review the
Coverage Map, competitive positioning recommendation, and Page Budget Table, and
approve the ToC before Phase 3 drafting begins. Resolve 5 content gaps before
handoff to drafting agent.© pnp, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis of pnp/sharepoint-skills.
Open the folder on GitHubat commit 69712d2
Rfp Response Strategy Synthesis 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 Strategy Synthesis this skillpnp/sharepoint-skills | 133 | — | ~6.9k | Automated safety check: Pass | MIT | |
| Authoring Rfdssymposium-dev/symposium | 249 | — | ~713 | Automated safety check: Pass | Custom licence | |
| Pfdskovalik/perception-first-design | 143 | — | ~7.3k | Automated safety check: Pass | Custom licence | |
| Yao Geo Trackingyaojingang/yao-geo-skills | 871 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Proposal Research Dossier Builderpawbytes/skill-suites | 113 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Japanese Writing DrafterChachamaru127/claude-code-harness | 3.2k | — | ~1.5k | Automated safety check: Notes | MIT |
symposium-dev/symposium
Write and structure RFDs (Requests for Discussion) for the Symposium project.
skovalik/perception-first-design
This skill should be used when working on any design, marketing, copywriting, writing, or communication task — including: "run PFD", "apply PFD", "use Perception-First Design", "do a PFD analysis"…
yaojingang/yao-geo-skills
Build a company-specific GEO backend tracking plan from a company name plus optional supporting information, using authoritative retrieval anchored on the official website, business-feature…
pawbytes/skill-suites
Turns a structured sales brief into an evidence-backed HTML research dossier, matching indexed case studies locally and gathering client, tech-stack and pricing evidence from the web.
Chachamaru127/claude-code-harness
Detect when the operator corrects the agent's Japanese phrasing mid-conversation (rewrites a sentence, calls out a style problem, says 'this wording is bad, say it like X instead') and draft a…
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
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…
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.
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.
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…
pnp/sharepoint-skills
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.
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.
Categories
Reads multiple input documents — past proposals, a win strategy brief, capability statements, a win/loss debrief, and RFP evaluation criteria — and synthesizes them into a recommended proposal Table…. Rfp Response Strategy Synthesis is an agent skill from pnp/sharepoint-skills. Reads multiple input documents — past proposals, a win strategy brief, capability statements, a win/loss debrief, and RFP evaluation criteria — and synthesizes them into a recommended proposal Table of Contents and a content strategy brief.
Rfp Response Strategy Synthesis fits situations like: tasks that involve Proposals and quotes; tasks that involve Content strategy.
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-strategy-synthesis -a claude-code`. Or copy the skill folder (Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis in pnp/sharepoint-skills) into .claude/skills/rfp-response-strategy-synthesis in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-strategy-synthesis -a codex`. Or copy the skill folder (Skills/rfp-response-strategy-synthesis/rfp-response-strategy-synthesis in pnp/sharepoint-skills) into .agents/skills/rfp-response-strategy-synthesis in your project. Codex loads it when a task matches its description.
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-strategy-synthesis -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-strategy-synthesis, .gemini/skills/rfp-response-strategy-synthesis, .github/skills/rfp-response-strategy-synthesis and .opencode/skills/rfp-response-strategy-synthesis in your project.
SKILL.md names no scripts, command-line tools or credentials: Rfp Response Strategy Synthesis is instructions for the agent only.
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.
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.
Rfp Response Strategy Synthesis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.9k tokens (SKILL.md is roughly 27k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Rfp Response Strategy Synthesis: Authoring Rfds (symposium-dev/symposium, 249 stars), Pfd (skovalik/perception-first-design, 143 stars), Yao Geo Tracking (yaojingang/yao-geo-skills, 871 stars) and Proposal Research Dossier Builder (pawbytes/skill-suites, 113 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 133 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 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.