Share Case

For detailed methodology guidance, see skills/research-literacy/SKILL.md.

⚠️ Verification Notice

This skill was generated by AI from academic literature. All parameters, thresholds, and citations require independent verification before use in research. If you find errors, please open an issue.

Prerequisites

This skill supports two submission methods:

1. Direct submission via gh CLI (Recommended)

   • Requires gh CLI installed and authenticated
   • Run gh auth status to check
   • Install from https://cli.github.com/ and run gh auth login

2. Manual submission via web browser

   • No gh CLI required
   • Opens GitHub Discussions page in browser
   • User copies and pastes the generated case

The skill will check for gh availability and let the user choose their preferred method.

GitHub Discussions must be enabled on the repository. The skill submits to the "Show & Tell" category.

Interactive Flow

Step 1 — Quick Survey

Present these questions using multiple-choice format:

Q1: Which skill did you use?

• Auto-detect from the current session context (list skills that were activated)
• Let the user confirm or select manually from the full skill list

Q2: What was your research scenario?

• Formal experiment
• Coursework or teaching
• Method exploration
• Paper reproduction
• Other (free text)

Q3: How helpful was the skill? (1-5)

• 1 = Not helpful
• 2 = Slightly helpful
• 3 = Moderately helpful
• 4 = Very helpful
• 5 = Extremely helpful

Q4: What was most valuable? (select all that apply)

• Correct methodology guidance
• Validated parameters and thresholds
• Pitfall warnings
• Complete pipeline coverage
• Literature references
• Other (free text)

Step 2 — Context Extraction

Extract the following from the current conversation:

1. Research context — The user's original research question and experimental setup
2. Key recommendations — The main suggestions the skill provided (parameters, methods, warnings)
3. Follow-up adjustments — Any modifications made during the conversation
4. Outcome summary — What the user ultimately decided to do

Format each as a concise paragraph. Do NOT include raw conversation transcripts — synthesize into readable summaries.

Step 3 — User Review and Submission Choice

Display the complete case preview using the format below.

First, check gh CLI availability:

gh auth status 2>&1

Then present submission options using AskUserQuestion:

If gh is available:

• Submit via gh CLI (Recommended) — Direct submission to GitHub Discussions
• Open in browser — Manual submission via web interface
• Delete sections — Remove specific paragraphs before submitting
• Anonymize — Replace specific names (datasets, labs, participants)
• Abort — Cancel without submitting

If gh is NOT available:

• Open in browser — Manual submission via web interface
• Delete sections — Remove specific paragraphs before submitting
• Anonymize — Replace specific names (datasets, labs, participants)
• Abort — Cancel without submitting

You MUST wait for explicit user confirmation before proceeding to Step 4.

Step 4 — Submit to GitHub

Based on the user's choice in Step 3:

Option A: Submit via gh CLI

Create a GitHub Discussion in the "Show & Tell" category.

First, get repository and category IDs:

gh api graphql -f query='
{
  repository(owner: "HaoxuanLiTHUAI", name: "awesome_cognitive_and_neuroscience_skills") {
    id
    discussionCategories(first: 10) {
      nodes {
        id
        name
      }
    }
  }
}'

Then create the discussion:

gh api graphql -f query='
mutation {
  createDiscussion(input: {
    repositoryId: "REPO_ID",
    categoryId: "SHOW_AND_TELL_CATEGORY_ID",
    title: "Community Case: SKILL_NAME",
    body: "CASE_BODY_HERE"
  }) {
    discussion {
      url
    }
  }
}'

On success, display the Discussion URL:

✅ Case shared successfully!
🔗 Discussion URL: [URL]

Thank you for contributing to the community!

On failure, fall back to Option B.

Option B: Open in Browser

1. Save the case locally to the current directory as case-skill-name-YYYYMMDD.md

2. Open the GitHub Discussions page:

xdg-open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/discussions/new?category=show-and-tell" 2>/dev/null || \
open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/discussions/new?category=show-and-tell" 2>/dev/null || \
echo "Please open: https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/discussions/new?category=show-and-tell"

3. Inform the user:

✅ Case saved to: case-skill-name-YYYYMMDD.md

🌐 Opening GitHub Discussions in your browser...

📋 Next steps:
1. Title: "Community Case: [Skill Name]"
2. Copy the content from case-skill-name-YYYYMMDD.md
3. Paste it into the discussion body
4. Click "Start discussion"

Thank you for contributing to the community!

Case Format Template

The submitted Discussion body uses this format:

## Community Case: [skill-name]

### Quick Info
- **Skill used**: `[skill-name]`
- **Scenario**: [selected option from Q2]
- **Rating**: [stars from Q3, e.g., ⭐⭐⭐⭐]
- **Most valuable**: [selected options from Q4]

### Research Context
> [User's research question and experimental setup — synthesized from conversation]

### What the Skill Suggested
- [Key recommendation 1]
- [Key recommendation 2]
- [Key recommendation 3]

### What I Actually Did & Result
> [User's experience applying the recommendations and the outcome]

### User's Tips
> [Optional: Additional insights the user wants to share with the community]

---
*Submitted via the `share-case` meta-skill.*

Privacy Principles

• Nothing is submitted without explicit user confirmation after full preview
• Users can remove any section or paragraph before submission
• Users can anonymize dataset names, lab names, and participant identifiers
• Users can choose to submit anonymously (no GitHub username attribution in the case body)
• The skill never auto-submits — the user must explicitly approve