feat(research): B2B customer discovery — 5 Stellar ecosystem products #28#39
Conversation
…ceprotocol#28 Reserve five active Stellar ecosystem products (Gearup, Reyts, GrantFox, Skyhitz, QuillTip) for customer discovery research with in-progress placeholder files following research/template.md.
📝 WalkthroughWalkthroughAdds five research markdown documents for GearUp, GrantFox, QuillTip, Reyts, and Skyhitz. Each file captures product metadata, follow-up tracking fields, discovery questions, synthesis placeholders, candidate assessments, contact channels, and outreach templates. ChangesProduct discovery research notes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…liceprotocol#28 Include verified contact channels and tailored opening messages for each of the five claimed Stellar ecosystem products to streamline interviews.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (3)
research/skyhitz.md (1)
8-8: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueSpecify single primary language for communication.
The template expects a single language selection (
[Español / Inglés / Otro]). "Inglés / Español" suggests bilingual outreach; pick the primary language or use "Otro" with clarification if both will be used interchangeably.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@research/skyhitz.md` at line 8, The communication language field is ambiguous because it lists both Inglés and Español instead of a single primary choice. Update the language selection in the template to use one clear option that matches the expected format in the document, and if bilingual communication is intended, switch to Otro with a brief clarification rather than listing both languages together.research/quilltip.md (2)
114-114: 📐 Maintainability & Code Quality | 🔵 TrivialFormat GitHub URL consistently or add protocol.
Line 114 uses
github.com/pragya-shar/quilltipwithouthttps://or@, unlike the product URL on Line 3. Standardize tohttps://github.com/pragya-shar/quilltipfor consistency and to ensure the link is clickable in rendered markdown.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@research/quilltip.md` at line 114, The GitHub link in the quilltip markdown is missing a protocol and is inconsistent with the other URL formatting. Update the GitHub entry in the document to use a fully qualified clickable URL, matching the style used by the product URL, and keep the reference text centered around the GitHub label in the markdown.
113-117: 📐 Maintainability & Code Quality | 🔵 TrivialNo direct team contact channel listed.
The "Canales de contacto identificados" only lists repository, website, and SCF round—no email, Discord, Twitter/X, or LinkedIn for the actual team. For effective outreach, identify and add a direct contact method (founder email, team Discord, Twitter/X DMs, or LinkedIn) before sending the opening message.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@research/quilltip.md` around lines 113 - 117, The contact section currently only lists indirect links like GitHub, the website, and funding info, but it does not include a direct way to reach the team. Update the “Canales de contacto identificados” entry in quilltip.md to add a real team contact method such as founder email, Discord, Twitter/X, or LinkedIn, and use the existing contact-listing block to keep the format consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@research/gearup.md`:
- Around line 114-117: The contact section in gearup.md includes a personal
phone number that should not be publicly exposed. Update the contact list entry
containing Tel so the number is removed, redacted, or replaced with a non-PII
placeholder, keeping the rest of the support/contact info intact. Use the
existing contact block near the Email/X/LinkedIn entries to locate and sanitize
the Tel field.
In `@research/quilltip.md`:
- Line 4: The QuillTip entry currently includes an unsourced award amount for
SCF Round 39, so update the `**Perfil SCF**` reference to either remove the
`$37,200 awarded` figure or replace it with a direct source-backed citation to
the specific award record. Keep the existing SCF submissions link or point it to
the exact grant/submission record so the amount is verifiable.
In `@research/skyhitz.md`:
- Around line 103-106: The rating in the “¿Es un candidato para Slice?” section
uses an invalid value, so update the summary in skyhitz.md to use one of the
template-compliant enums only. Change the current “Media-Alta” label to a valid
value from Alta / Media / Baja, and make sure it aligns with the downstream fit
used by docs/research/customer-discovery.md or clearly reflects the chosen enum
in the same section.
---
Nitpick comments:
In `@research/quilltip.md`:
- Line 114: The GitHub link in the quilltip markdown is missing a protocol and
is inconsistent with the other URL formatting. Update the GitHub entry in the
document to use a fully qualified clickable URL, matching the style used by the
product URL, and keep the reference text centered around the GitHub label in the
markdown.
- Around line 113-117: The contact section currently only lists indirect links
like GitHub, the website, and funding info, but it does not include a direct way
to reach the team. Update the “Canales de contacto identificados” entry in
quilltip.md to add a real team contact method such as founder email, Discord,
Twitter/X, or LinkedIn, and use the existing contact-listing block to keep the
format consistent.
In `@research/skyhitz.md`:
- Line 8: The communication language field is ambiguous because it lists both
Inglés and Español instead of a single primary choice. Update the language
selection in the template to use one clear option that matches the expected
format in the document, and if bilingual communication is intended, switch to
Otro with a brief clarification rather than listing both languages together.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 3210a5e3-0ed7-40b6-9242-60a782df9469
📒 Files selected for processing (5)
research/gearup.mdresearch/grantfox.mdresearch/quilltip.mdresearch/reyts.mdresearch/skyhitz.md
| - Email: support@gearup.market | ||
| - X: @Gearupmarket | ||
| - LinkedIn: Mary Odogbo (Co-founder & CEO), Obasi Ifegwu (Co-founder) | ||
| - Tel: +234 912 166 8550 |
There was a problem hiding this comment.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
Remove or mask the phone number to protect PII.
Publishing a personal phone number (+234 912 166 8550) in a public repository exposes identifiable contact information and may violate privacy expectations. Replace with a placeholder, redact the number, or move it to a private notes system.
- - Tel: +234 912 166 8550
+ - Tel: [redacted — see private notes]📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - Email: support@gearup.market | |
| - X: @Gearupmarket | |
| - LinkedIn: Mary Odogbo (Co-founder & CEO), Obasi Ifegwu (Co-founder) | |
| - Tel: +234 912 166 8550 | |
| - Email: support@gearup.market | |
| - X: `@Gearupmarket` | |
| - LinkedIn: Mary Odogbo (Co-founder & CEO), Obasi Ifegwu (Co-founder) | |
| - Tel: [redacted — see private notes] |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@research/gearup.md` around lines 114 - 117, The contact section in gearup.md
includes a personal phone number that should not be publicly exposed. Update the
contact list entry containing Tel so the number is removed, redacted, or
replaced with a non-PII placeholder, keeping the rest of the support/contact
info intact. Use the existing contact block near the Email/X/LinkedIn entries to
locate and sanitize the Tel field.
| # QuillTip | ||
|
|
||
| **URL del producto**: https://quilltip.me | ||
| **Perfil SCF**: https://communityfund.stellar.org/submissions (SCF Round 39, $37,200 awarded) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify QuillTip SCF submission details
curl -s "https://communityfund.stellar.org/submissions" | grep -i "quilltip\|pragya-shar" | head -20Repository: sliceprotocol/slice-stellar
Length of output: 165
🌐 Web query:
QuillTip Stellar Community Fund Round 39 37200 site:communityfund.stellar.org OR site:communityfund.stellar.org/submissions
💡 Result:
QuillTip is a project focused on publishing and microtipping on the Stellar network [1][2]. It was listed as a participant in Stellar Community Fund (SCF) Round 39 [3][4][5]. Regarding the number 37200, there is no direct public reference linking this specific number to a QuillTip submission or award amount within the Stellar Community Fund records found. It is possible this number relates to an internal submission ID, a specific transaction hash, or a different metric not publicly displayed in the project's summary pages [2]. The SCF does not explicitly list submission IDs or grant amounts in the format of "37200" on its public project portals [3][5].
Citations:
- 1: https://communityfund.stellar.org/project/quilltip-publishing-and-microtipping-tjn
- 2: https://communityfund.stellar.org/submissions/reckPFhE8GyZuqJHo
- 3: https://communityfund.stellar.org/projects?tab=round-10
- 4: https://communityfund.stellar.org/projects?tab=round-9
- 5: https://communityfund.stellar.org/projects
🌐 Web query:
"QuillTip" "Community Fund" Stellar
💡 Result:
QuillTip is a decentralized, open-source publishing platform designed to allow writers to earn money through reader tips [1][2]. The project utilizes the Stellar blockchain to enable ultra-low fee micropayments [3]. QuillTip has received support from the Stellar Community Fund (SCF), an initiative operated by the Stellar Development Foundation to support developers and startups building on the Stellar and Soroban networks [4][5][6]. The project has been recognized as an SCF-funded initiative [5] and has participated in the SCF submission process, where it was highlighted for leveraging Stellar's network capabilities to facilitate instant micropayments [3]. Technical details for the project, including its codebase, are publicly available on GitHub, where it is noted as being built with Next.js 16 and a Convex backend [1][2].
Citations:
- 1: https://github.com/pragya-shar/quilltip
- 2: https://github.com/pragya-shar/quilltip/blob/main/README.md
- 3: https://communityfund.stellar.org/submissions/reckPFhE8GyZuqJHo
- 4: https://communityfund.stellar.org/project/quilltip-publishing-and-microtipping-tjn
- 5: https://lumenloop.com/projects/quilltip
- 6: https://stellar.gitbook.io/scf-handbook
Replace the award amount with a source-backed reference. QuillTip is listed in SCF Round 39, but the “$37,200 awarded” figure needs a direct citation; otherwise remove it or link the specific award record.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@research/quilltip.md` at line 4, The QuillTip entry currently includes an
unsourced award amount for SCF Round 39, so update the `**Perfil SCF**`
reference to either remove the `$37,200 awarded` figure or replace it with a
direct source-backed citation to the specific award record. Keep the existing
SCF submissions link or point it to the exact grant/submission record so the
amount is verifiable.
| ## ¿Es un candidato para Slice? | ||
|
|
||
| **Media-Alta** — Creator economy platforms face rights and payment disputes; subjective evaluation of deliverables aligns with Slice's juror model. | ||
|
|
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Use template-compliant rating value.
The template specifies the rating must be one of Alta / Media / Baja. "Media-Alta" is not a valid value and also conflicts with the downstream consumer table's expected fit of ⭐⭐ Medio (docs/research/customer-discovery.md). Reconcile with the downstream source or justify the upgrade, but use the prescribed enum.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@research/skyhitz.md` around lines 103 - 106, The rating in the “¿Es un
candidato para Slice?” section uses an invalid value, so update the summary in
skyhitz.md to use one of the template-compliant enums only. Change the current
“Media-Alta” label to a valid value from Alta / Media / Baja, and make sure it
aligns with the downstream fit used by docs/research/customer-discovery.md or
clearly reflects the chosen enum in the same section.
2 participants
Summary
Draft PR for issue #28 — [Product Discovery] Customer Discovery B2B — 5 Stellar Ecosystem Products #5.
Adds 5 research placeholder files reserving active Stellar ecosystem products for customer discovery interviews.
Products claimed
All 5 products are SCF-funded or actively operating in the Stellar ecosystem, have real users, and meet ≥2 criteria from the issue (P2P value exchange, fulfillment-based fund release, strangers as parties, bad-faith incentives).
Status
🔄 In progress — placeholder files created. Outreach to product teams pending.
Closes #28
Test plan
research/template.mdstructureSummary by CodeRabbit