Agent skill

Rfp Response Quality Tone Review

by pnp in 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.

MITAuto-check passedSales & Support

Install Rfp Response Quality Tone Review

skills CLI
$ npx skills add pnp/sharepoint-skills --skill rfp-response-quality-tone-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pnp/sharepoint-skills rfp-response-quality-tone-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
rfp-response-quality-tone-review
GitHub stars
133
Token cost
~3.5k tokens
SKILL.md length
1,386 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Reviews a draft proposal for voice consistency, narrative coherence, the firm's configurable tone standards, weak or vague language, and structural quality.

  • Works in 6 steps: Load the Draft and Inputs → Assess Narrative Coherence → Section-by-Section Quality Review → …
  • Tasks that involve Proposals and quotes
  • SKILL.md covers Firm Profile (REQUIRED — fill…, Purpose, Firm Voice Standards (EXAMPLE… and Step 1 — Load the Draft and…, plus 6 more sections
  • Reaches contoso.sharepoint.com

What it does

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.

When your agent uses it

  • Tasks that involve Proposals and quotes
  • Tasks that involve Cloud office suites
  • Tasks that involve Code review

Example prompts

  • “Use the rfp-response-quality-tone-review skill to review a draft proposal for voice consistency, narrative coherence, the firm's configurable tone…”
  • “/rfp-response-quality-tone-review”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Load the Draft and Inputs
  2. Assess Narrative Coherence
  3. Section-by-Section Quality Review
  4. Line-Level Language Review
  5. Log Findings
  6. Report Back to the User

What it can do on your machine

Read from SKILL.md and the folder at commit 69712d2. 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 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.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

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 69712d2, republished under its MIT licence (© pnp). 1,386 words, ~3,483 tokens.

Download SKILL.mdSave it as .claude/skills/rfp-response-quality-tone-review/SKILL.md (or your agent's skills folder).
name
rfp-response-quality-tone-review
description
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.

Quality & Tone Review 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]
  • NAMED METHODOLOGY: [optional — e.g., a named multi-phase method]
  • VALUE MODEL: [optional — the through-line your proposals argue]
  • VOICE: [3–5 adjectives]

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 VOICE values above. Keep the structure; change the content.


Purpose

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.


Firm Voice Standards (EXAMPLE — customize for your firm)

Every quality finding is evaluated against these standards. Replace the examples with your own before use.

What the Firm's Voice Sounds Like

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.

QualityDescriptionExample
SpecificClaims anchored to facts, frameworks, or named methodology"Our delivery framework begins with a structured readiness assessment" — not "We take a comprehensive approach"
Risk-awareAcknowledges complexity and risk honestly"Adoption at this scale presents change-management challenges that require clear decision rights before rollout"
Outcome-orientedExplains what the client will do differently"Following the design phase, the organization will have a defensible, audit-ready governance structure"
AccountableCommitments clear and tied to the firm's scope"We will deliver a framework and a knowledge-transfer plan — not a deployed system"
Consistent with positioningVoice reflects the firm's VENDOR STANCE"We will facilitate an objective evaluation of options against your defined requirements"
What the Firm's Voice Does Not Sound Like
PatternProblemFlag Severity
Vague superlatives: "comprehensive", "holistic", "robust", "seamless" without substanceFiller signaling lack of specificityMedium
Promotional enthusiasm: "exciting opportunity", "transformative potential", "game-changing"Inconsistent with a risk-disciplined toneMedium
Language crossing the ROLE BOUNDARY: "we will configure", "we will roll out" (for an advisory firm)Blurs positioningHigh (escalate to Compliance Review if not already flagged)
First-person plural without clarity of role: "we will ensure" (ensure what? at what scope?)Ambiguous accountabilityMedium
Passive construction obscuring accountability: "the framework will be designed"Firm must be the named actor in its own commitmentsLow
Padded sentences: "It is worth noting that…", "It should be mentioned that…"Weakens authority; delete the preambleLow
Client flattery: "Your organization's forward-thinking approach…"Unprofessional in formal proposalsMedium

Step 1 — Load the Draft and Inputs

  1. Retrieve the compliance-reviewed and salesperson-corrected draft from the WIP Collaboration Folder.
  2. Retrieve resolved and open Review Findings for this proposal (Compliance) — do not re-flag logged compliance issues; reference them only if they have a quality dimension not previously captured.
  3. Retrieve the approved Content Strategy Brief (Phase 2) — assess the draft against the approved strategy, not just standalone quality.

Step 2 — Assess Narrative Coherence

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:

  • Does the exec summary make a clear, specific value proposition that the body sections substantiate?
  • Is there logical progression across sections — does the argument build, or repeat?
  • Does the proposal answer the evaluator's implicit question: "Why this firm, for this engagement, for this client, at this moment?"
  • If the Firm Profile defines a VALUE MODEL, is it reflected in the overall structure?

Log coherence gaps as findings (Step 5). A coherence gap requires structural changes, not line edits.


Step 3 — Section-by-Section Quality Review

For each section:

3a — Opening and Framing

  • Opens with relevance to the client's challenge — not a self-introduction or methodology description?
  • First sentence specific enough to orient the reader?
  • Flag inside-out framings ("[FIRM NAME] has extensive experience…", "Our approach is…"). Open from the client's perspective, then introduce the firm's response.

3b — Specificity and Evidence

  • Does each substantive claim have a specific anchor (named methodology phase, referenced past engagement type, cited standard/framework)?
  • Flag two or more consecutive sentences with no specific evidence, framework reference, or outcome.
  • Flag "extensive" without a quantifier or example.

3c — Differentiator Reinforcement

  • Cross-reference each section against the differentiators the Content Strategy Brief prioritised. Confirm each prioritised differentiator is present in at least one section with substantive language — not a one-line mention. Flag any that is absent from the full document.

3d — Transition and Flow

  • Do sections connect logically (last sentence sets up the next, or the next heading signals progression)?
  • Flag consecutive sections readable in any order without loss of meaning — suggests a missing narrative arc.

3e — Length and Proportionality

  • Are sections proportional to the weight of the corresponding evaluation criterion? A 30% criterion should not get one paragraph while a 10% criterion gets a full page.
  • Cross-reference section word counts against the evaluation weighting from Phase 2 (and the Page Budget Table, if present). Flag significant disproportionality.
  • Flag sections over 600 words (Word) or 2 content slides (PowerPoint) that could be condensed without loss of substance.

Show full SKILL.md (472 more words)Show less

Step 4 — Line-Level Language Review

Mechanical checks — flag every instance.

Weak Language Patterns (Low or Medium)
PatternAction
"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
Tone Inconsistencies (Medium)
  • Promotional language in body sections (acceptable in exec summary preamble only if balanced)
  • Casual register in formal sections (contractions, colloquialisms)
  • Inconsistent second-person address: mixing "the organization" and "you" in the same section
Terminology Consistency (Low)

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:

TermStandard Usage (example)
Named methodology phasesAlways the same names and casing (from Firm Profile NAMED METHODOLOGY)
The clientClient'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

Step 5 — Log Findings

For each issue, create an item in the Review Findings list:

FieldValue
ProposalProposal name (link to a Proposals tracking item)
Review TypeQuality & Tone
SeverityHigh (coherence gaps, missing critical differentiators) / Medium (tone, structure) / Low (line-level)
LocationSection name and paragraph or slide number
FindingDescription of the quality issue
Verbatim textThe exact phrase or sentence flagged
Recommended fixSpecific rewrite suggestion where possible
StatusOpen

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"

Step 6 — Report Back to the User

Provide a summary with:

  • Total findings by severity.
  • Any High findings (coherence gaps, missing critical differentiators) listed explicitly — require structural changes.
  • Count of prioritised differentiators confirmed vs. absent.
  • Terminology consistency status (pass/fail per term).
  • Proportionality assessment: over-/under-weighted sections relative to evaluation criteria.
  • URL of the annotated draft and the Review Findings list.
Example Summary Output
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.

Notes & Edge Cases

  • Highly technical proposals: Be more tolerant of technical language, but still flag jargon a non-technical evaluator on the buyer's panel would struggle to assess.
  • PowerPoint proposals: Focus on slide headline quality (each headline a complete, specific statement — not a topic label), bullet specificity, and narrative flow across slide order. Flag any bullet longer than 15 words on a slide face.
  • Salesperson voice vs. firm voice: Highly personalized language ("I've worked with many organizations like yours…") is acceptable in a cover letter or intro email, not in the formal proposal body. Flag these as Medium.
  • Re-running after corrections: On re-run, carry forward unresolved findings. Only re-check sections the salesperson edited — do not re-score the full document unless explicitly requested.

© 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-quality-tone-review/rfp-response-quality-tone-review of pnp/sharepoint-skills.

Open the folder on GitHubat commit 69712d2

Compare with similar skills

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.

Rfp Response Quality Tone Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rfp Response Quality Tone Review this skillpnp/sharepoint-skills133—~3.5kAutomated safety check: PassMIT
AirweaveCraftOS-dev/CraftBot392—~1.1kAutomated safety check: PassMIT
Proposal GenerationJoelLewis/finance_skills206—~8.8kAutomated safety check: PassMIT
Task Profiletechwolf-ai/ai-first-toolkit132—~3.6kAutomated safety check: PassMIT
Paw Pa Generationpawbytes/skill-suites113—~2.3kAutomated safety check: PassMIT
Learn From Correctionassafkip/kipi-system112—~2.3kAutomated safety check: PassMIT

Similar skills

  • Airweave

    CraftOS-dev/CraftBot

    Context retrieval layer for AI agents across users' applications.

    392 GitHub stars~1.1k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Proposal Generation

    JoelLewis/finance_skills

    Generate end-to-end investment proposals covering risk profiling, model portfolio recommendation, fee illustration, projections, and compliance review.

    206 GitHub stars~8.8k tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed
  • Task Profile

    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…

    132 GitHub stars~3.6k tokensUpdated 11 days ago
    Sales & SupportAuto-check passed
  • Paw Pa Generation

    pawbytes/skill-suites

    Assembles branded, export-ready proposals from brief, research, and pricing artifacts — type-adaptive for pitch, RFP, or scoping.

    113 GitHub stars~2.3k tokensUpdated 8 days ago
    Sales & SupportAuto-check passed
  • Learn From Correction

    assafkip/kipi-system

    Propose a principle edit to a skill or persona file based on a (agentoutput, humanoutput) correction pair.

    112 GitHub stars~2.3k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 40 repos~3.2k tokens
    Sales & SupportAuto-check passed

More from pnp/sharepoint-skills

All 52 skills in this repo
  • 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…

    133 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • 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.

    133 GitHub stars~899 tokensUpdated yesterday
    Auto-check passed
  • 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.

    133 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • 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…

    133 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Dossier

    pnp/sharepoint-skills

    Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.

    133 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • 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.

    133 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Questions about Rfp Response Quality Tone Review

What does Rfp Response Quality Tone Review do?

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.

When should I use Rfp Response Quality Tone Review?

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.

How do I install Rfp Response Quality Tone Review in Claude Code?

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.

How do I install Rfp Response Quality Tone Review in Codex?

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.

Can I use Rfp Response Quality Tone Review 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-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.

What does Rfp Response Quality Tone Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Rfp Response Quality Tone Review is instructions for the agent only.

Does Rfp Response Quality Tone Review 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 Quality Tone Review 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 Quality Tone Review use?

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.

How many tokens does Rfp Response Quality Tone Review use?

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.

What are the alternatives to Rfp Response Quality Tone Review?

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.

Who maintains Rfp Response Quality Tone Review?

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.