scf-tranche-reporter

Writes SCF Build Award tranche submission reports documenting deliverables and completion evidence.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/stellar-zk/stellar-zk --skill scf-tranche-reporter-stellar-zk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scf-tranche-reporter
Source: https://github.com/stellar-zk/stellar-zk/tree/main/.claude/skills/scf-tranche-reporter
Command: npx skills add https://github.com/stellar-zk/stellar-zk --skill scf-tranche-reporter-stellar-zk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Funded Stellar Community Fund teams must submit milestone deliverables for review before each tranche payment is released, and insufficient documentation is the most common cause of approval delays. This Skill structures tranche submissions so reviewers can verify completion criteria quickly. ## Core Features & Use Cases - Deliverable Documentation: Maps each promised deliverable to concrete evidence such as contract addresses, repo commits, test results, and demo links. - Completion Criteria Mapping: Explicitly states how each criterion from the original application was met, with status and proof. - Milestone-Specific Guidance: Covers T1 MVP, T2 Testnet, and T3 Mainnet requirements including mandatory UX readiness at T3. - Use Case: A team that just deployed their Soroban contract to testnet uses this Skill to produce a T2 submission with contract addresses, passing CI links, and deviation notes formatted the way SCF reviewers expect. ## Quick Start Write my SCF T2 tranche submission report for my project, documenting the deployed testnet contract, API endpoints, and completion criteria evidence.

Frequently Asked Questions about scf-tranche-reporter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an SCF tranche submission report?▼

List each deliverable from your original application, map every completion criterion to concrete evidence like contract addresses, repo commits, and test results, then disclose any deviations from the plan. Submit through the SCF Build Tranche Completion Form emailed after your T0 payment.

What evidence do SCF tranche reviewers expect for deliverables?▼

Evidence depends on deliverable type: deployed contract addresses and passing test suites for smart contracts, live URLs or demo recordings for frontends, published packages for SDKs, and transaction hashes for integrations. On-chain evidence like block explorer links is strongest.

What are the SCF Build Award tranche payment percentages?▼

T0 pays 10% automatically on award approval, T1 pays 20% after MVP milestone approval, T2 pays 30% after Testnet milestone approval, and T3 pays 40% after Mainnet deliverables including UX readiness are approved.

Why do SCF tranche submissions get delayed or rejected?▼

Delays are most commonly caused by insufficient documentation, not incomplete work. Common issues include broken links, private repos without reviewer access, vague evidence like "see the repo", undisclosed scope changes, and missing UX readiness at T3.

What is required for the T3 Mainnet tranche in SCF?▼

T3 requires mainnet deployment, mandatory UX readiness with functional interfaces and usable onboarding, comprehensive end-user documentation, and launch readiness with adoption metrics or a launch plan. UX readiness has been mandatory since SCF 7.0.