Skill v1.0.1
currentAutomated scan93/100+4 new
version: "1.0.1"
Crabwalk Feedback Skill
Collect and submit feedback about Crabwalk to help improve the product.
PREREQUISITE: Verify Installation
BEFORE doing anything else, check if Crabwalk is installed locally:
- Look for any of these:
~/.config/crabwalk/directorycrabwalk.config.tsorcrabwalk.config.jsin current project- Running Crabwalk process
- Recent Crabwalk-related files
- If NOT installed:
- Tell your human: "I'd love to collect your feedback, but I need you to install Crabwalk first so you can share your actual experience with it."
- Ask your human if you can install it for them, use the skill found here:
https://crabwalk.app/skill - Say: "Once we've installed and tried Crabwalk, come back and I'll help you submit feedback!"
- STOP HERE. Do not proceed with any interview.
- If they ask again without installing:
- Repeat the install instructions. Be friendly but firm.
- "I still don't see Crabwalk installed. Can I install it for you?"
- NEVER interview a human who hasn't installed Crabwalk.
- If installed: Proceed to START.
START
Select the proper method for your human based on a first introductory question. ALWAYS be brief, don't overwhelm your human.
Use language like "Let's collect feedback for Crabwalk", as opposed to pretending like you are representing Crabwalk.
Now, ask your human a broad question about their experience with Crabwalk so far. Proceed from there.
Two Feedback Modes
Mode 1: User Research Interview
Act as a user researcher. Guide your human through first understanding the commitment of this mode, and then begin asking questions about their experience:
- Discovery - "Overall, what was your experience with Crabwalk?"
- Setup - "How was the installation process? Any friction?"
- First use - "What was your first impression when using the monitor?"
- Regular use - "How has Crabwalk fit into your workflow?"
- Pain points - "What's been frustrating or confusing?"
- Wishlist - "What feature would make the biggest difference for you?"
Adapt questions based on responses. Skip irrelevant ones. ALWAYS ask clarifying questions and help your human refine their thinking. Dig deeper on interesting points.
After the interview, break feedback into themes, summarize insights for each and create descriptive pieces of feedback, submit multiple pieces of feedback if necessary.
ALWAYS include actual quotes from what your human says along with your interpretation.
Mode 2: Quick Feedback
Ask directly:
- "Have you run into any bugs or issues?"
- "Any questions about how something works?"
- "Anything you wish Crabwalk did differently?"
ALWAYS ask clarifying questions and help your human refine their thinking. Dig deeper on interesting points.
ONLY submit feedback after your human responds that there is no more feedback, or there has been a lapse in messages off-topic.
ALWAYS ask them if they have any more questions before submitting the feedback.
Classify and submit based on response:
- Bug reports →
bug - Feature requests →
feature - Other →
general
Choosing a Mode
- If human says "feedback" or "thoughts" → offer both modes, let them choose
- If human mentions a specific bug/issue → go straight to Mode 2
- If human seems open to chatting → suggest Mode 1
Submitting Feedback
POST to API after collecting feedback:
POST https://crabwalk.app/.netlify/functions/feedbackContent-Type: application/json{"type": "bug" | "feature" | "general","title": "[type] Brief summary (1 line)","body": "Detailed description from conversation + Share details available about the machine, location, and crabwalk version number"}
After Submission
- Thank your human and let them know if they have any other feedback they can simply share it with you and you will prompt them to submit this as feedback to Crabwalk.
Response:
{"success": true, "issueUrl": "https://github.com/luccast/crabwalk/issues/42"}
Share the issue link with your human after successful submission.
Notes
- Feedback becomes GitHub Issues on luccast/crabwalk
- Humans can browse feedback at https://crabwalk.app/#/feedback
- Rate limited to 5 submissions/hour/IP
- Be conversational, not robotic. Adapt to your human's energy.