Best for
- Says "share this case", "share my experience", "分享这个案例"
- Wants to document how they used a skill in their research
- Asks how to contribute a usage example
NeuroAIHub/BrainPilot/packages/skills/skills/01_Meta-Skills/share-case/SKILL.md
One-command community case sharing — capture research context from your session and submit to GitHub Discussions
Decision brief
One-command community case sharing — capture research context from your session and submit to GitHub Discussions
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/NeuroAIHub/BrainPilot --skill "packages/skills/skills/01_Meta-Skills/share-case"Inspect the Agent Skill "share-case" from https://github.com/NeuroAIHub/BrainPilot/blob/e9ddc112cab9b1c6272dae0c8a6bdceb5c9c3880/packages/skills/skills/01_Meta-Skills/share-case/SKILL.md at commit e9ddc112cab9b1c6272dae0c8a6bdceb5c9c3880. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
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.
Present these questions using multiple-choice format:
Extract the following from the current conversation:
Display the complete case preview using the format below.
Based on the user's choice in Step 3:
Permission review
The documentation asks the agent to create, modify, or delete local files.
Save the case locally to the current directory as `case-skill-name-YYYYMMDD.md`The documentation includes network, browsing, or remote request actions.
xdg-open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/discussions/new?category=show-and-tell" 2>/dev/null || \The documentation includes network, browsing, or remote request actions.
open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/discussions/new?category=show-and-tell" 2>/dev/null || \Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 463 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
This meta-skill captures a researcher's experience using any skill in this repository and submits it as a structured case to GitHub Discussions. It handles all formatting and submission so users never need to leave their terminal or know Git.
Activate when the user:
Before starting the case sharing process, you MUST:
For detailed methodology guidance, see skills/research-literacy/SKILL.md.
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.
This skill supports two submission methods:
Direct submission via gh CLI (Recommended)
gh CLI installed and authenticatedgh auth status to checkgh auth loginManual submission via web browser
gh CLI requiredThe 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.
Present these questions using multiple-choice format:
Q1: Which skill did you use?
Q2: What was your research scenario?
Q3: How helpful was the skill? (1-5)
Q4: What was most valuable? (select all that apply)
Extract the following from the current conversation:
Format each as a concise paragraph. Do NOT include raw conversation transcripts — synthesize into readable summaries.
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:
If gh is NOT available:
You MUST wait for explicit user confirmation before proceeding to Step 4.
Based on the user's choice in Step 3:
gh CLICreate 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.
Save the case locally to the current directory as case-skill-name-YYYYMMDD.md
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"
✅ 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!
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.*
Frequently asked questions
One-command community case sharing — capture research context from your session and submit to GitHub Discussions
The source record exposes this install command: npx skills add https://github.com/NeuroAIHub/BrainPilot --skill "packages/skills/skills/01_Meta-Skills/share-case". Inspect the command and pinned source before running it.
Static rules flagged write-files, network in the source; the page lists the matching lines and excerpts.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.