More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Project Notes-to-Proof Page

    1

    Convert approved project notes into a privacy-aware case-study page with traceable claims and honest unknowns.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Project Notes-to-Proof Page

    Project Notes-to-Proof Page

    Example session with this skill installed

    Turn these intake-redesign notes into an anonymized portfolio case study. Keep the client fictional, distinguish delivered work from observed or measured outcomes, preserve privacy boundaries, and do not claim production efficiency, revenue, adoption, causation, or client approval unless supplied.

    • Read your context and instructions
    • Compiled the project notes-to-proof page

    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>Northstar Studio — Demonstration Case Study</title>
      <style>
        :root{--navy:#12233f;--blue:#4169e1;--paper:#f5f3ed;--green:#2f725d;--line:#d8d4c9}
        *{box-sizing:border-box}body{margin:0;background:var(--paper);color:var(--navy);font-family:Arial,sans-serif;line-height:1.6}
        main{max-width:1060px;margin:auto;padding:30px}.label{display:inline-block;background:var(--navy);color:white;padding:7px 11px;font-size:12px;letter-spacing:.06em}
        header{padding:64px 0 42px}h1{font-size:clamp(40px,6vw,72px);line-height:1.04;margin:20px 0;max-width:900px}h2{font-size:30px;margin-bottom:10px}
        section{padding:42px 0;border-top:1px solid var(--line)}.split{display:grid;grid-template-columns:1fr 1fr;gap:22px}.panel{background:white;border:1px solid var(--line);padding:24px}
        .before{border-top:5px solid #aa5149}.after{border-top:5px solid var(--green)}.metric{font-size:48px;font-weight:800}.tag{color:var(--green);font-weight:700;font-size:12px}
        .tree{background:var(--navy);color:white;padding:24px;font-family:monospace;white-space:pre-wrap;overflow:auto}.warning{border-left:4px solid #aa5149;padding-left:18px}
        @media(max-width:720px){.split{grid-template-columns:1fr}main{padding:18px}}
      </style>
    </head>
    <body>
    <main>
      <header>
        <span class="label">Demonstration Output — fictional data, not supplied by the user</span>
        <h1>From seven intake handoffs to one visible owner at every step.</h1>
        <p>Northstar Studio, a fictional three-person architecture practice, used a documented prototype to simplify how new project inquiries move from first contact to internal review.</p>
      </header>
    
      <section>
        <h2>The constraint</h2>
        <p>The supplied fictional notes described duplicated questions, unclear ownership, and seven documented handoff steps. No production timing, revenue, lead-volume, or client-satisfaction data was supplied.</p>
      </section>
    
      <section>
        <h2>Same-case before and after</h2>
        <div class="split">
          <article class="panel before"><div class="tag">BEFORE · N01–N03</div><div class="metric">7</div><h3>Documented handoff steps</h3><p>Inquiry details moved through email, a shared note, and an internal checklist with unclear transition ownership.</p></article>
          <article class="panel after"><div class="tag">PROTOTYPE · A01</div><div class="metric">4</div><h3>Prototype workflow steps</h3><p>A single intake summary assigns an owner, review state, missing information, and the next internal decision.</p></article>
        </div>
      </section>
    
      <section>
        <h2>What was actually delivered</h2>
        <div class="split">
          <div class="panel"><h3>Intake structure</h3><p>One set of client-facing questions and an internal summary mapped to the same fields.</p></div>
          <div class="panel"><h3>Ownership states</h3><p>New, needs information, ready for review, and decision recorded.</p></div>
        </div>
      </section>
    
      <section>
        <h2>Evidence and confidence</h2>
        <div class="tree">CASE STUDY PROOF
    ├─ Starting condition
    │  ├─ Claim: seven documented handoff steps
    │  └─ Evidence: N01,N02 | Confidence: HIGH
    ├─ Intervention
    │  ├─ Deliverable: four-step prototype workflow
    │  └─ Evidence: A01 | Confidence: HIGH
    ├─ Outcomes
    │  ├─ Measured: none supplied
    │  ├─ Observed: stakeholder notes reported clearer ownership
    │  │  └─ Evidence: N04 | Confidence: MEDIUM
    │  └─ Unknown: production time, revenue, conversion, adoption
    └─ Publication state
       └─ DEMONSTRATION — fictional and not client-approved</div>
      </section>
    
      <section>
        <h2>Honest outcome</h2>
        <p class="warning"><strong>Confirmed within the fictional artifact:</strong> the prototype reduced the documented workflow from seven steps to four and made ownership states visible. <strong>Not established:</strong> production efficiency, business impact, user adoption, or causation.</p>
      </section>
    
      <section>
        <h2>Privacy &amp; provenance audit</h2>
        <pre>PRIVACY PROVENANCE AUDIT v1.1
    B01 — DEMONSTRATION: fictional organization; no client identity supplied
    N01–N04 — project observations; publication authority not established
    A01 — prototype artifact; approved only for this fictional demonstration
    Verdict: DEMONSTRATION — CLIENT APPROVAL NOT APPLICABLE</pre>
      </section>
    
      <section>
        <h2>Could your intake tell the same clear story?</h2>
        <p>Next action: review one current project intake and identify the first ownership break.</p>
      </section>
    </main>
    </body>
    </html>
    
    

    Next step: review the evidence ledger and release blockers before using the asset externally.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Strong project work often stays trapped in notes. When it becomes a case study, missing evidence is easily polished into impact claims and privacy boundaries disappear.

    What this skill delivers

    Project Notes-to-Proof Page converts supplied notes and approved artifacts into a self-contained HTML proof page. It separates context, constraints, delivered intervention, before and after, measured outcomes, observed change, unavailable impact, claim IDs, confidence rationale, privacy state, and one CTA.

    Why it is different

    • Every public claim links to supplied evidence.
    • Confidence means evidence coverage, not marketing certainty.
    • Separates measured, observed, and unavailable outcomes.
    • Runs a Privacy-Provenance Gate before creator review.

    Included

    Source Skill, worked HTML demonstration, executable validator, and a six-page English buyer guide inside the ZIP.

    Boundaries

    No invented approval, quotes, metrics, causation, anonymity guarantee, client contact, or publication.

    Does not guarantee legal anonymity or invent client approval, quotes, metrics, causation, or business impact. It does not publish or contact a client; inaccessible evidence remains missing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    This skill automates the transition from messy internal documentation to professional case studies by mapping every claim to specific evidence, ensuring you never overstate impact or compromise sensitive data.

    The ZIP file includes the Source Skill, a fully rendered HTML demonstration, an executable validator for your output, and a comprehensive six-page English buyer's guide to get you started.

    This skill is designed to work with most leading LLMs (like GPT-4 or Claude 3.5) that support large context windows for processing detailed project notes and documentation.

    The 'Privacy-Provenance Gate' is a built-in check that identifies sensitive information and verifies that every claim in the final page is backed by your uploaded notes before you even see the draft.

    While it generates a high-fidelity HTML proof page, the skill will never invent metrics, fabricate client quotes, or assume causality where the data doesn't explicitly show it.