Airweave
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
Reviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality.
$ npx skills add pnp/sharepoint-skills --skill rfp-response-quality-tone-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-quality-tone-review --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-quality-tone-review/rfp-response-quality-tone-review .claude/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .claude/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-review/rfp-response-quality-tone-reviewType 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-quality-tone-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-quality-tone-review --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-quality-tone-review/rfp-response-quality-tone-review .agents/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .agents/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-quality-tone-review --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-quality-tone-review/rfp-response-quality-tone-review .cursor/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .cursor/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-review/rfp-response-quality-tone-review--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-quality-tone-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pnp/sharepoint-skills rfp-response-quality-tone-review --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-quality-tone-review/rfp-response-quality-tone-review .gemini/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .gemini/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-reviewInstalls 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-quality-tone-review -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-quality-tone-review/rfp-response-quality-tone-review .github/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .github/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-review -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-quality-tone-review --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-quality-tone-review/rfp-response-quality-tone-review .opencode/skills/rfp-response-quality-tone-review && 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-quality-tone-review" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review into .opencode/skills/rfp-response-quality-tone-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rfp-response-quality-tone-review", 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-quality-tone-reviewReviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality.
Rfp Response Quality Tone Review is an agent skill from pnp/sharepoint-skills. Reviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality. Runs after compliance review and salesperson corrections. Logs findings to the Review Findings SharePoint list and annotates the draft.
Its SKILL.md is about 3.5k 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, Cloud office suites and Code review. It works with Microsoft SharePoint. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.
6 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.
Hosts in commands or code, which the agent is likely to contact:
contoso.sharepoint.comFrom 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 Quality Tone Review loads about 3.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,386 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). 1,386 words, ~3,483 tokens.
.claude/skills/rfp-response-quality-tone-review/SKILL.md (or your agent's skills folder).These values define who your firm is and how it writes. See SETUP.md.
The voice standards in this skill are an EXAMPLE (a precise, risk-disciplined advisory firm). Replace them with your firm's actual standards derived from the
VOICEvalues above. Keep the structure; change the content.
A proposal that passes compliance may still fail on quality. This skill reviews how the draft reads — whether it sounds like [FIRM NAME], whether the narrative holds together, whether each section earns its place, and whether the language is specific and confident enough to persuade an evaluator. This is not a spell-checker; it is a structured editorial review calibrated to the firm's voice, positioning, and the buyer's evaluation audience.
Every quality finding is evaluated against these standards. Replace the examples with your own before use.
Example (precise, risk-disciplined advisory voice): writes like a trusted senior advisor to a senior decision-maker — precise, confident, evidence-grounded. Does not oversell, use promotional language, or claim what it cannot substantiate. Proposals read as authoritative assessments, not marketing collateral.
| Quality | Description | Example |
|---|---|---|
| Specific | Claims anchored to facts, frameworks, or named methodology | "Our delivery framework begins with a structured readiness assessment" — not "We take a comprehensive approach" |
| Risk-aware | Acknowledges complexity and risk honestly | "Adoption at this scale presents change-management challenges that require clear decision rights before rollout" |
| Outcome-oriented | Explains what the client will do differently | "Following the design phase, the organization will have a defensible, audit-ready governance structure" |
| Accountable | Commitments clear and tied to the firm's scope | "We will deliver a framework and a knowledge-transfer plan — not a deployed system" |
| Consistent with positioning | Voice reflects the firm's VENDOR STANCE | "We will facilitate an objective evaluation of options against your defined requirements" |
| Pattern | Problem | Flag Severity |
|---|---|---|
| Vague superlatives: "comprehensive", "holistic", "robust", "seamless" without substance | Filler signaling lack of specificity | Medium |
| Promotional enthusiasm: "exciting opportunity", "transformative potential", "game-changing" | Inconsistent with a risk-disciplined tone | Medium |
| Language crossing the ROLE BOUNDARY: "we will configure", "we will roll out" (for an advisory firm) | Blurs positioning | High (escalate to Compliance Review if not already flagged) |
| First-person plural without clarity of role: "we will ensure" (ensure what? at what scope?) | Ambiguous accountability | Medium |
| Passive construction obscuring accountability: "the framework will be designed" | Firm must be the named actor in its own commitments | Low |
| Padded sentences: "It is worth noting that…", "It should be mentioned that…" | Weakens authority; delete the preamble | Low |
| Client flattery: "Your organization's forward-thinking approach…" | Unprofessional in formal proposals | Medium |
Before individual sections, assess the proposal as a whole. Read the executive summary, then the first paragraph of each body section, then the closing. Ask:
Log coherence gaps as findings (Step 5). A coherence gap requires structural changes, not line edits.
For each section:
3a — Opening and Framing
3b — Specificity and Evidence
3c — Differentiator Reinforcement
3d — Transition and Flow
3e — Length and Proportionality
Mechanical checks — flag every instance.
| Pattern | Action |
|---|---|
| "comprehensive", "holistic", "robust" (unsubstantiated) | Replace with specific descriptor |
| "seamless", "frictionless", "smooth" | Output promises, not advisory commitments |
| "innovative", "cutting-edge", "state-of-the-art" (without specifics) | Replace with what is specifically novel |
| "partner with" (client relationship) | Use "advise", "support", or "work alongside" (adjust to positioning) |
| "It is worth noting that" / "It should be mentioned" | Delete preamble, start with the substance |
| "going forward" | Replace with "from this point" or restructure |
| Sentences beginning "We believe…" | Assert, do not believe — replace with an evidence-backed statement |
Check key terms are used consistently throughout — inconsistency suggests the proposal was assembled from multiple sources without review. Build this table from your firm's standard terminology; example rows:
| Term | Standard Usage (example) |
|---|---|
| Named methodology phases | Always the same names and casing (from Firm Profile NAMED METHODOLOGY) |
| The client | Client's formal name on first reference per section; "the organization" thereafter |
| "Engagement" vs. "project" | "Engagement" for the firm's work; "project" may refer to the client's initiative |
For each issue, create an item in the Review Findings list:
| Field | Value |
|---|---|
| Proposal | Proposal name (link to a Proposals tracking item) |
| Review Type | Quality & Tone |
| Severity | High (coherence gaps, missing critical differentiators) / Medium (tone, structure) / Low (line-level) |
| Location | Section name and paragraph or slide number |
| Finding | Description of the quality issue |
| Verbatim text | The exact phrase or sentence flagged |
| Recommended fix | Specific rewrite suggestion where possible |
| Status | Open |
Also add an inline annotation at each finding's location:
[QUALITY FLAG — Severity: Medium | Tone: Vague superlative]
"robust governance framework" — replace with specific description of what makes the framework defensible.
Suggested: "a governance framework with defined decision rights, documented escalation paths, and quarterly audit review cycles"Provide a summary with:
Quality & Tone Review complete.
Findings summary:
High severity: 2
Medium severity: 9
Low severity: 14
HIGH — Structural changes required:
1. Narrative coherence gap — Executive summary value proposition not substantiated
in Section 3 (Approach). Section 3 reads as methodology description, not a
response to the client's stated challenge. Recommend restructuring Section 3
opening to connect explicitly to the client's priority identified in the RFP.
2. Differentiator absent — "Structured knowledge transfer model" not reinforced
anywhere in the document. This is a priority differentiator per the Content
Strategy Brief. Suggest adding 1 paragraph to Section 6.
MEDIUM — Address before final publication:
3. [Exec Summary] "Your organization's progressive approach to AI" — client flattery, remove
4. [Section 2] "Seamless integration of governance controls" — outcome promise, reframe
5. [Section 3] Three consecutive sentences with no evidence anchor — add framework ref
6. [Section 4] "We believe our methodology is well-suited…" — rewrite as assertion
7. [Section 5] "Innovative risk tiering approach" — specify what is novel
8. [Section 5] Mixes "the organization" and "you" — standardize to "the organization"
9. [Section 6] Section is 820 words; evaluation weight is 10% — consider condensing
10. [Section 7] "Partner with the organization" — replace with "advise the organization"
11. [Appendix A] "Comprehensive case study portfolio" — unsubstantiated; use count
LOW — Recommended improvements: 14 findings (see Review Findings list)
Differentiator coverage:
Vendor-neutral independence — present
Domain specialization — present
Embedded security integration — present
Structured knowledge transfer model — ABSENT ← High finding #2
Decision-quality methodology — present
Terminology consistency:
Methodology phase names — consistent
"Engagement" vs. "project" — consistent
Capitalization of key terms — inconsistent (6 instances — standardize)
Client name usage — consistent
Review Findings logged:
https://contoso.sharepoint.com/sites/Proposals/Lists/ReviewFindings
Annotated draft:
https://contoso.sharepoint.com/sites/Proposals/WIP/NorthwindRFP/Northwind_Proposal_DRAFT_QualityAnnotated.docx
Next steps: Salesperson addresses High and Medium findings, then submits for
final formatting before publication.© 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-quality-tone-review/rfp-response-quality-tone-review of pnp/sharepoint-skills.
Open the folder on GitHubat commit 69712d2
Rfp Response Quality Tone Review 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 Quality Tone Review this skillpnp/sharepoint-skills | 133 | — | ~3.5k | Automated safety check: Pass | MIT | |
| AirweaveCraftOS-dev/CraftBot | 392 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Proposal GenerationJoelLewis/finance_skills | 206 | — | ~8.8k | Automated safety check: Pass | MIT | |
| Task Profiletechwolf-ai/ai-first-toolkit | 132 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Paw Pa Generationpawbytes/skill-suites | 113 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Learn From Correctionassafkip/kipi-system | 112 | — | ~2.3k | Automated safety check: Pass | MIT |
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
JoelLewis/finance_skills
Generate end-to-end investment proposals covering risk profiling, model portfolio recommendation, fee illustration, projections, and compliance review.
techwolf-ai/ai-first-toolkit
Mine the user's Claude Code + Cowork session history into a structured task profile, what they do with AI, how often, how successfully where friction lives, then propose atomic skills that would…
pawbytes/skill-suites
Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping.
assafkip/kipi-system
Propose a principle edit to a skill or persona file based on a (agentoutput, humanoutput) correction pair.
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.
Works with
Categories
Reviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality. Rfp Response Quality Tone Review is an agent skill from pnp/sharepoint-skills. Reviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality.
Rfp Response Quality Tone Review fits situations like: tasks that involve Proposals and quotes; tasks that involve Cloud office suites; tasks that involve Code review.
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-quality-tone-review -a claude-code`. Or copy the skill folder (Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review in pnp/sharepoint-skills) into .claude/skills/rfp-response-quality-tone-review in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pnp/sharepoint-skills --skill rfp-response-quality-tone-review -a codex`. Or copy the skill folder (Skills/rfp-response-quality-tone-review/rfp-response-quality-tone-review in pnp/sharepoint-skills) into .agents/skills/rfp-response-quality-tone-review 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-quality-tone-review -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-quality-tone-review, .gemini/skills/rfp-response-quality-tone-review, .github/skills/rfp-response-quality-tone-review and .opencode/skills/rfp-response-quality-tone-review in your project.
SKILL.md names no scripts, command-line tools or credentials: Rfp Response Quality Tone Review is instructions for the agent only.
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.
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 Quality Tone Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k 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 Quality Tone Review: Airweave (CraftOS-dev/CraftBot, 392 stars), Proposal Generation (JoelLewis/finance_skills, 206 stars), Task Profile (techwolf-ai/ai-first-toolkit, 132 stars) and Paw Pa Generation (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.