Source profileQuality 92/100

NeuroAIHub/BrainPilot/packages/skills/skills/01_Meta-Skills/share-case/SKILL.md

share-case

One-command community case sharing — capture research context from your session and submit to GitHub Discussions

Source repository stars
463
Declared platforms
0
Static risk flags
2
Last source update
2026-08-25
Source checked
2026-08-28

Decision brief

What it does: where it fits

One-command community case sharing — capture research context from your session and submit to GitHub Discussions

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

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/NeuroAIHub/BrainPilot --skill "packages/skills/skills/01_Meta-Skills/share-case"
Safe inspection promptEditorial

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

What the source asks the agent to do

  1. 01

    ⚠️ 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.

    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.
  2. 02

    Step 1 — Quick Survey

    Present these questions using multiple-choice format:

    Auto-detect from the current session context (list skills that were activated)Let the user confirm or select manually from the full skill listFormal experiment
  3. 03

    Step 2 — Context Extraction

    Extract the following from the current conversation:

    Research context — The user's original research question and experimental setupKey recommendations — The main suggestions the skill provided (parameters, methods, warnings)Follow-up adjustments — Any modifications made during the conversation
  4. 04

    Step 3 — User Review and Submission Choice

    Display the complete case preview using the format below.

    Submit via gh CLI (Recommended) — Direct submission to GitHub DiscussionsOpen in browser — Manual submission via web interfaceDelete sections — Remove specific paragraphs before submitting
  5. 05

    Step 4 — Submit to GitHub

    Based on the user's choice in Step 3:

    Save the case locally to the current directory as case-skill-name-YYYYMMDD.mdOpen the GitHub Discussions page:Inform the user:

Permission review

Static risk signals and limitations

Writes files

medium · line 180

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`

Network access

medium · line 184

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 || \

Network access

medium · line 185

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

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score92/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars463SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
NeuroAIHub/BrainPilot
Skill path
packages/skills/skills/01_Meta-Skills/share-case/SKILL.md
Commit
e9ddc112cab9b1c6272dae0c8a6bdceb5c9c3880
License
AGPL-3.0
Collected
2026-08-28
Default branch
main
View the original SKILL.md

Share Case

Purpose

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.

When to Use This Skill

Activate when the user:

  • 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

Research Planning Protocol

Before starting the case sharing process, you MUST:

  1. Identify the skill used — Which skill(s) from this repository were used in the current session?
  2. Clarify sharing scope — What aspects of the experience does the user want to share?
  3. Declare what will be extracted — List the specific conversation elements that will be included
  4. Note privacy considerations — Are there dataset names, lab identifiers, or participant details that should be anonymized?
  5. Present the extraction plan to the user and WAIT for confirmation before proceeding.

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"
  1. 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

Frequently asked questions

What to verify before installation and use

What does the share-case source document cover?

One-command community case sharing — capture research context from your session and submit to GitHub Discussions

How do I install share-case?

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.

Which permission-related actions were detected?

Static rules flagged write-files, network in the source; the page lists the matching lines and excerpts.

Alternatives

Compare before choosing

Computed 10045,960

coreyhaines31/marketingskills

ab-testing

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

Computed 10045,960

coreyhaines31/marketingskills

churn-prevention

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

Computed 10025,136

alirezarezvani/claude-skills

app-store-optimization

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

Computed 10015,385

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.