More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Skill-to-Marketplace Proof Pack

    1

    Align a completed Skill, listing, worked demo, screenshots, buyer guide, and claim ledger before release.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Skill-to-Marketplace Proof Pack

    Skill-to-Marketplace Proof Pack

    Example session with this skill installed

    Turn this completed meeting-decision Skill and its recorded fictional cold run into a low-ticket marketplace proof pack. Keep the listing, worked request/result, three proof shots, buyer-guide outline, and claim ledger aligned. Remove unsupported cross-model, time-savings, sales, acceptance, and runtime claims.

    • Read your context and instructions
    • Compiled the -to-marketplace proof

    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.

    
    # Demonstration Output — Marketplace Proof Pack
    
    Fictional data, not supplied by the user. No upload, pricing save, submission,
    review, publication, install, or purchase occurred.
    
    ## Artifact identity
    
    - Runtime: fictional `meeting-decision-extractor`
    - Buyer job: turn supplied meeting notes into a decision register.
    - Evidence available: structural parse and one fictional cold-run output.
    - Evidence unavailable: independent runtime, cross-model, marketplace, and buyer
      evidence.
    - Price position: $5 low-ticket hypothesis, not an optimal-price finding.
    
    ## Listing draft
    
    ### Title
    
    Meeting Decision Extractor — Owners, Due Dates & Open Questions
    
    ### Short description
    
    Turn messy meeting notes into a clear decision register with named owners, due
    dates, unresolved questions, and an explicit missing-evidence section.
    
    ### Buyer problem
    
    The meeting ends, but the notes still mix discussion, decisions, requests, and
    ideas. Owners disappear into paragraphs and unresolved questions look complete.
    
    ### Concrete outcome
    
    Paste supplied notes and receive one structured register separating:
    
    - confirmed decisions;
    - actions and named owners;
    - due dates explicitly present in the notes;
    - open questions;
    - missing owner or date fields.
    
    ### How it works
    
    1. Separates statements by decision state.
    2. Preserves exact owner and date evidence.
    3. Marks missing fields instead of guessing.
    4. Returns a compact register ready for human review.
    
    ### Honest boundary
    
    It does not record meetings, identify speakers not named in the notes, contact
    participants, update calendars, or prove that an action was completed.
    
    ### CTA
    
    Install once and turn your next note dump into a reviewable decision register.
    
    ## Worked buyer request
    
    ```text
    
    **Use these notes**
    - We agreed to ship the onboarding copy after legal review.
    - Nina owns the revised draft for Friday.
    - The pricing page question is still open.
    - Someone should confirm the analytics event names.
    

    Worked result

    MEETING DECISION REGISTER — Demonstration Output
    
    DECISION D01
    **State:** CONDITIONAL
    **Decision:** Ship the onboarding copy after legal review.
    **Owner:** UNKNOWN
    **Due date:** UNKNOWN
    **Dependency:** Legal review
    
    ACTION A01
    **Action:** Prepare the revised onboarding copy.
    **Owner:** Nina
    **Due date:** Friday — exact calendar date not supplied
    **Dependency:** D01
    
    OPEN QUESTION Q01
    **Question:** What decision is required for the pricing page?
    **Owner:** UNKNOWN
    
    OPEN QUESTION Q02
    **Question:** Who will confirm the analytics event names?
    **Owner:** UNKNOWN
    
    **VERDICT:** READY FOR HUMAN REVIEW — no calendar or message action occurred
    

    Three-shot proof sequence

    Screenshot 1 — Before / Input

    • Headline: Your meeting notes are not a decision system.
    • Visual: the exact four-line buyer request with discussion and ownership mixed.
    • Evidence badge: FICTIONAL DEMONSTRATION INPUT.
    • Proves: recognizable problem and low-friction input.
    • Alt text: Four fictional meeting-note bullets containing a conditional
      decision, one named owner, and two unresolved questions.

    Screenshot 2 — After / Output

    • Headline: Decisions, owners, dates, and unknowns—separated.
    • Visual: D01, A01, Q01, and Q02 from the same result.
    • Evidence badge: SAME-CASE DEMONSTRATION OUTPUT.
    • Proves: the promised structure and visible missing-data behavior.
    • Alt text: Structured fictional decision register with one conditional
      decision, one action assigned to Nina, and two open questions.

    Screenshot 3 — Mechanism / Boundary

    • Headline: It marks what the notes do not prove.
    • Visual: dependency line, unknown owner/date fields, and external-action boundary.
    • Evidence badge: STRUCTURAL + FICTIONAL COLD RUN ONLY.
    • Proves: evidence discipline and scope.
    • Alt text: Close view of missing fields and the statement that no calendar or
      participant contact action occurred.

    Buyer-guide outline

    1. What problem the Skill owns.
    2. Quick start with one note block.
    3. Supported inputs and maximum input count.
    4. Decision, action, and question states.
    5. How unknown owners and dates are handled.
    6. Complete worked example.
    7. What the Skill does not do.
    8. Support path and safe reporting information.

    Claim cards

    ┌─ CLAIM CARD C01 ────────────────────────────────────────┐
    │ Claim: turns supplied notes into a decision register    │
    │ Support: runtime instruction + fictional cold run       │
    │ Status: SUPPORTED AS DEMONSTRATION                      │
    
    

    │ Dependency: Worked result -> Screenshot 2 │
    └──────────────────────────────────────────────────────────┘

    
    ┌─ CLAIM CARD C02 ────────────────────────────────────────┐
    │ Claim: works across AI agents                            │
    │ Support: no cross-model evidence                         │
    │ Status: REMOVE                                           │
    
    

    │ Dependency: compatibility field -> FAQ │
    └──────────────────────────────────────────────────────────┘

    
    ┌─ CLAIM CARD C03 ────────────────────────────────────────┐
    │ Claim: saves hours                                       │
    │ Support: no time study                                   │
    │ Status: REMOVE                                           │
    │ Dependency: title and short description                 │
    └──────────────────────────────────────────────────────────┘
    

    Release blockers

    • Platform field limits and current policy: UNVERIFIED.
    • Independent runtime execution: NOT RUN.
    • Cross-model behavior: NOT RUN.
    • Final package security preflight: NOT RUN in this fictional demonstration.
    • Visual assets: specified, not rendered.

    Signal screen

    ✓ Runtime owner: fictional completed Skill
    ✓ Listing/demo alignment: same buyer job and same case
    ✓ Proof state: structural parse + fictional cold run only
    ✓ External state: no upload or publication claim
    ✗ Remaining gate: current marketplace constraints and independent runtime
    
    **VERDICT:** DEMONSTRATION — RUNTIME EVIDENCE NEEDED
    

    Release dependency gate

    RELEASE DEPENDENCY GATE v1.1
    **Runtime owner:** PRESENT — fictional Meeting Decision Extractor
    **Worked request/result pair:** PRESENT — demonstration only
    **Proof shots:** 3/3 SPECIFIED — not rendered screenshots
    **Validation evidence:** STRUCTURAL FIXTURE CHECK ONLY
    **External state:** LOCAL DRAFT — no upload, submission, approval, sale, or purchase
    **Release verdict:** HOLD FOR CREATOR REVIEW
    

    Next action: run the completed runtime independently on the worked request before
    using any runtime-tested claim.

    
    **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

    A technically solid Skill can reach a marketplace with generic copy, decorative screenshots, stale claims, and a demo that does not match its recorded behavior.

    What this skill delivers

    Skill-to-Marketplace Proof Pack turns a completed SKILL.md and recorded evidence into aligned listing copy, one executable buyer request, one complete same-case result, three proof-shot specifications, a buyer-guide outline and FAQ, claim-to-runtime evidence cards, release blockers, and one next action.

    Why it is different

    • Starts after the runtime exists and does not pretend to rebuild it.
    • Connects listing, demo, screenshots, and runtime evidence.
    • Separates passed, defined, blocked, and unverified claims.
    • Runs a Release-Dependency Gate before creator review.

    Included

    Source Skill, complete worked proof pack, executable validator, and a six-page English buyer guide inside the ZIP.

    Boundaries

    No runtime changes, invented tests or compatibility, marketplace acceptance claim, upload, submission, pricing action, or publication.

    Does not build or change the runtime Skill; invent tests, compatibility, sales, reviews, or acceptance; verify current marketplace rules without a live check; upload, price, submit, or publish.

    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 resolves the 'last-mile' gap between a functional tool and a professional marketplace listing by aligning your SKILL.md and recorded evidence into a cohesive set of proof-shots, buyer guides, and verified claim ledgers.

    The Proof Pack requires a completed Skill (SKILL.md) and recorded evidence of its behavior; it does not perform any runtime modifications, code changes, or actual marketplace submissions.

    You will receive a ZIP file containing the Source Skill, a complete worked proof pack, an executable validator, and a comprehensive six-page English buyer guide.

    Yes, the Proof Pack includes a Release-Dependency Gate that categorizes claims as passed, defined, blocked, or unverified to ensure your demo matches actual recorded behavior.

    While the guide is delivered in English, the alignment logic and evidence cards can be applied to any AI agent skill that utilizes a standardized SKILL.md format and verifiable runtime logs.

    The Proof Pack acts as a pre-release auditor; it identifies release blockers and aligns your documentation, but it does not handle the pricing, uploading, or final publication to the marketplace.