Token导航 LogoToken导航TokenDH.com
研究检索操作浏览器github未标认证来源可访问许可证需确认审计通过

share-case分享案例

Agent Skill

share-case 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

30,862

周安装

728

GitHub Stars

20

下载量

10,154
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:share-case(分享案例)
来源仓库:https://github.com/haoxuanlithuai/awesome_cognitive_and_neuroscience_skills
仓库路径:skills/share-case
安装命令:
npx skills add https://github.com/haoxuanlithuai/awesome_cognitive_and_neuroscience_skills --skill 'Share Case'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/haoxuanlithuai/awesome_cognitive_and_neuroscience_skills --skill 'Share Case'

简介

share-case 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx skills add 命令安装,需结合原始 README 核验具体用法。
  • 安装前建议确认权限范围、维护状态及是否触发联网或文件读写操作。
  • 当前无额外底部简介内容,可参考来源仓库进一步了解功能细节。

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

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.49%
按下载量换算3,604

Claude

30.8%
按下载量换算3,127

Cursor

20.83%
按下载量换算2,115

Gemini CLI

9.11%
按下载量换算925

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills