More screenshots
Works with the AI tools you already use
Prospect-to-Proposal Microsite
Turn verified prospect context and seller evidence into a source-backed proposal microsite with one CTA.
$5
Prospect-to-Proposal Microsite
Example session with this skill installed
Use this bakery's public page, my catering inquiry-page service, and a 20-minute discovery review to create a proposal microsite. Separate verified prospect facts, seller-supplied claims, hypotheses, and unknowns. Do not invent pain points, metrics, urgency, or conversion outcomes.
- Read your context and instructions
- Compiled the prospect-to-proposal microsite
- Generated the UI component
Complete demonstration
This is the same-case worked artifact shipped with the Skill. It preserves the evidence boundaries and does not claim publication or commercial results.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Harbor & Pine — Demonstration Proposal</title>
<style>
:root{--ink:#241a16;--cream:#fffaf2;--rose:#b95049;--sage:#5d755f;--line:#e8d9c9}
*{box-sizing:border-box}body{margin:0;background:var(--cream);color:var(--ink);font-family:Arial,sans-serif;line-height:1.6}
main{max-width:1040px;margin:auto;padding:32px}header{padding:72px 0 44px;border-bottom:1px solid var(--line)}
.label{display:inline-block;padding:6px 10px;border:1px solid var(--rose);color:var(--rose);font-size:12px;letter-spacing:.08em;text-transform:uppercase}
h1{font-family:Georgia,serif;font-size:clamp(42px,7vw,78px);line-height:1.02;max-width:860px;margin:22px 0}h2{font-family:Georgia,serif;font-size:34px;margin-bottom:8px}
.lead{font-size:20px;max-width:720px}.cta{display:inline-block;margin-top:20px;padding:13px 18px;background:var(--rose);color:white;text-decoration:none;border-radius:3px}
section{padding:48px 0;border-bottom:1px solid var(--line)}.grid{display:grid;grid-template-columns:repeat(3,1fr);gap:18px}.card{padding:22px;background:white;border:1px solid var(--line)}
.source{font-size:12px;color:var(--sage);font-weight:bold}.steps{counter-reset:s}.step{display:grid;grid-template-columns:52px 1fr;gap:16px;margin:20px 0}.step:before{counter-increment:s;content:counter(s);display:grid;place-items:center;width:42px;height:42px;border-radius:50%;background:var(--sage);color:white}
.ledger{font-family:monospace;background:#241a16;color:#fffaf2;padding:24px;white-space:pre-wrap}.boundary{border-left:4px solid var(--rose);padding-left:18px}
@media(max-width:760px){main{padding:20px}.grid{grid-template-columns:1fr}header{padding-top:42px}}
</style>
</head>
<body>
<main>
<header>
<span class="label">Demonstration Output — fictional data, not supplied by the user</span>
<h1>Make catering requests feel as considered as the cakes.</h1>
<p class="lead">A focused inquiry experience for Harbor & Pine that turns celebration and wholesale interest into clear, reviewable requests.</p>
<a class="cta" href="#agenda">Review the 20-minute discovery agenda</a>
</header>
<section>
<h2>What we noticed</h2>
<div class="grid">
<article class="card"><div class="source">P01 · SOURCE_BACKED</div><h3>Celebration demand is visible</h3><p>The fictional source includes celebration-order content and custom product examples.</p></article>
<article class="card"><div class="source">P02 · SOURCE_BACKED</div><h3>Wholesale has its own path</h3><p>A wholesale page signals business demand, but it is separate from event catering.</p></article>
<article class="card"><div class="source">H01 · INFERRED</div><h3>Catering intent may be leaking</h3><p>No dedicated catering inquiry path was visible in the fictional sample. This is a hypothesis for discovery, not a confirmed loss.</p></article>
</div>
</section>
<section>
<h2>Where the offer fits</h2>
<p>A single catering inquiry page can collect date, guest range, service type, dietary needs, and response preference before the first call. The proposed lead-routing setup is seller-supplied scope, not a Harbor & Pine commitment.</p>
<div class="steps">
<div class="step"><div><strong>Clarify</strong><br>Confirm catering offer, capacity boundaries, and the questions staff actually need.</div></div>
<div class="step"><div><strong>Prototype</strong><br>Build one mobile-first inquiry page and an internal request summary.</div></div>
<div class="step"><div><strong>Review</strong><br>Test the fictional workflow with sample inquiries before any live change.</div></div>
</div>
</section>
<section>
<h2>Proof without pretending</h2>
<p class="boundary"><strong>No client result is claimed.</strong> This demonstration shows a proposal structure only. Production deployment, response time, lead quality, and business impact remain unverified.</p>
</section>
<section id="agenda">
<h2>20-minute discovery agenda</h2>
<div class="grid">
<div class="card"><strong>5 min</strong><br>Current catering demand and request sources</div>
<div class="card"><strong>10 min</strong><br>Required fields, capacity limits, and routing owner</div>
<div class="card"><strong>5 min</strong><br>Prototype scope and review decision</div>
</div>
</section>
<section>
<h2>Evidence ledger</h2>
<div class="ledger">EVIDENCE COMPLETENESS: ███████░░░ 7/10 material claims supported
ACCOUNT FIT: ██████░░░░ evidence-supported with one visible hypothesis
CTA READINESS: ██████████ clear seller-selected next action
P01 SOURCE_BACKED — celebration-order content in fictional source
P02 SOURCE_BACKED — wholesale page in fictional source
S01 SELLER_SUPPLIED — catering inquiry page and routing setup
H01 INFERRED — catering intent may lack a dedicated path
ACCOUNT FIT RISK LEDGER v1.1
Source coverage: P01,P02
Seller dependency: S01
Hypothesis requiring discovery: H01
Risk verdict: HYPOTHESIS VISIBLE — confirm before outreach
VERDICT: DEMONSTRATION — READY FOR SELLER REVIEW, NOT SENT OR PUBLISHED</div>
</section>
</main>
</body>
</html>
Next step: review the evidence ledger and release blockers before using the asset externally.
prospect-to-proposal-microsite.tsx
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Generic proposals make the buyer do the relevance work. They describe the seller but rarely show what was actually observed about the specific account.
What this skill delivers
Prospect-to-Proposal Microsite turns supplied public prospect context, verified seller evidence, and one next action into a self-contained HTML proposal page. It includes evidence IDs, account observations, labelled fit hypotheses, a proposed engagement path, one CTA, blockers, and an evidence ledger.
Why it is different
- Separates prospect facts, seller claims, inference, and unknowns before writing.
- Requires evidence IDs for visible account claims.
- Checks seller dependencies and prohibited performance guarantees.
- Produces a seller-review verdict before external use.
Included
Source Skill, worked HTML demonstration, executable validator, and a six-page English buyer guide inside the ZIP.
Boundaries
No cloning, hosting, outreach, publication, invented metrics, urgency, testimonials, or conversion guarantees.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 22 days ago
- Passed all security checks, Safe to install