agentleFS
NeuroAIHubNeuroAIHub/awesome_cognitive_and_neuroscience_skills/skills/share-case/SKILL.md

share-case

Skill39 starsChanged 9 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before starting the case sharing process, you MUST:

    line 27
  2. Very specific:

    Run gh auth status to check

    line 49
  3. Distinctive:

    GitHub Discussions: must be enabled on the repository.

    line 59
  4. Very specific:

    If gh is available:

    line 118
  5. Very specific:

    If gh is NOT available:

    line 125
  6. Distinctive:

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

    line 139
  7. Distinctive:

    Nothing is submitted without explicit user confirmation: after full preview

    line 249

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.