@brainpilot/skills 0.0.6

package/dist/index.d.ts

@@ -0,0 +1,6 @@
+/**
+ * Absolute path to the bundled skills/ directory. Lives at the package root,
+ * one level above the compiled `dist/` (or `src/`) dir.
+ */
+export declare const BUNDLED_SKILLS_DIR: string;
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAwBA;;;GAGG;AACH,eAAO,MAAM,kBAAkB,QAA2C,CAAC"}

package/dist/index.js

@@ -0,0 +1,28 @@
+/**
+ * @brainpilot/skills — bundled Agent Skills content package.
+ *
+ * This package is pure CONTENT: the `skills/` directory holds the built-in
+ * neuroscience / cognitive-science / writing skills as `SKILL.md` files (with
+ * YAML frontmatter `name` / `description`), laid out as `<category>/<skill>/SKILL.md`.
+ *
+ * Skills are NOT served through a custom tool or MCP server anymore. They are
+ * loaded through Pi's NATIVE skill pipeline (`DefaultResourceLoader`'s
+ * `additionalSkillPaths`), which already implements progressive disclosure
+ * (skill name+description in the system prompt, body read on demand). At deploy
+ * time the runtime/CLI materialize these files into `<dataDir>/bp_template/skills/`
+ * (user-editable), and Pi loads from there.
+ *
+ * The only thing this module exports is the absolute path to the bundled
+ * `skills/` directory, so the runtime/CLI can locate it for materialization via
+ * `require.resolve("@brainpilot/skills")` regardless of install layout
+ * (workspace symlink, flat npm node_modules, or Docker image).
+ */
+import { fileURLToPath } from "node:url";
+import { dirname, join, resolve } from "node:path";
+const __dirname = dirname(fileURLToPath(import.meta.url));
+/**
+ * Absolute path to the bundled skills/ directory. Lives at the package root,
+ * one level above the compiled `dist/` (or `src/`) dir.
+ */
+export const BUNDLED_SKILLS_DIR = resolve(join(__dirname, "..", "skills"));
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AACH,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEnD,MAAM,SAAS,GAAG,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC;AAE1D;;;GAGG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,OAAO,CAAC,IAAI,CAAC,SAAS,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC,CAAC"}

package/package.json

@@ -0,0 +1,35 @@
+{
+  "name": "@brainpilot/skills",
+  "version": "0.0.6",
+  "engines": {
+    "node": ">=22"
+  },
+  "license": "Apache-2.0",
+  "type": "module",
+  "description": "BrainPilot built-in Agent Skills content (neuroscience / cognitive-science / writing), loaded via Pi's native skill pipeline",
+  "main": "./dist/index.js",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "default": "./dist/index.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist",
+    "skills"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/NeuroAIHub/BrainPilot.git",
+    "directory": "packages/skills"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsc -b",
+    "typecheck": "tsc -b"
+  }
+}

package/skills/01_Meta-Skills/contribute-skill/SKILL.md

@@ -0,0 +1,277 @@
+---
+name: "contribute-skill"
+description: "One-command skill contribution — generate a SKILL.md from your domain expertise and submit to GitHub Issues for maintainer review"
+domain: "meta-skill"
+version: "1.0.0"
+review_status: "ai-generated"
+dependencies:
+  recommended:
+    - paper-to-skill
+    - research-literacy
+---
+
+# Contribute Skill
+
+## Purpose
+
+This meta-skill lets researchers contribute new domain knowledge skills to the repository without needing Git expertise. It generates a properly formatted SKILL.md from the user's domain knowledge and submits it as a GitHub Issue for maintainer review.
+
+## When to Use This Skill
+
+Activate when the user:
+
+- Says "contribute a skill", "把这个方法做成 skill", "submit a new skill"
+- Wants to turn a discussion about methodology into a reusable skill
+- Has domain expertise they want to encode as a structured skill
+- Wants to contribute a skill from a paper they are reading
+
+---
+
+## Research Planning Protocol
+
+Before starting the contribution process, you MUST:
+
+1. **Identify the knowledge source** — Where does this domain knowledge come from? (paper, personal expertise, current session)
+2. **Confirm domain specificity** — Does this knowledge pass the litmus test: "Would a competent programmer who has never taken a cognitive science course get this wrong?"
+3. **Outline the expected skill structure** — What sections and parameters will the skill contain?
+4. **Note potential gaps** — What information might be missing or need verification?
+5. **Present the contribution 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](https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues).
+
+---
+
+## 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 Issues page in browser
+   - User copies and pastes the generated content
+
+The skill will check for `gh` availability and let the user choose their preferred method.
+
+---
+
+## Interactive Flow
+
+### Step 1 — Source Confirmation
+
+**Q1: Where does this knowledge come from?**
+- A specific paper (provide DOI or title)
+- Personal research experience
+- Current session discussion
+- Textbook or guidelines document
+- Other (free text)
+
+**Q2: What is the skill about?** (free text — brief description of the methodology)
+
+**Q3: Suggested skill name?**
+- Auto-suggest a kebab-case name based on the description
+- Let the user confirm or modify
+
+**If the source is a paper with DOI/title**, check whether the `paper-to-skill` meta-skill would be more appropriate. If the user has the full paper available, suggest: "Since you have the full paper, the `paper-to-skill` skill can do a more thorough extraction. Would you like to use that instead?"
+
+### Step 2 — Content Generation
+
+Generate a SKILL.md following the project conventions. The generated skill MUST include:
+
+**YAML Frontmatter:**
+```yaml
+---
+name: "[Human-Readable Skill Name]"
+description: "[One-sentence summary]"
+domain: "[subdomain]"
+version: "1.0.0"
+review_status: "ai-generated"
+papers:
+  - "[Author, Year]"
+dependencies:
+  required:
+    - research-literacy
+---
+```
+
+**Required Sections (in order):**
+
+1. **Purpose** — What domain knowledge this skill encodes
+2. **When to Use This Skill** — Trigger conditions
+3. **Research Planning Protocol** — Standard preamble (adapt from template):
+
+   ```
+   ## Research Planning Protocol
+
+   Before executing the domain-specific steps below, you MUST:
+
+   1. **State the research question** — What specific question is this analysis/paradigm addressing?
+   2. **Justify the method choice** — Why is this approach appropriate? What alternatives were considered?
+   3. **Declare expected outcomes** — What results would support vs. refute the hypothesis?
+   4. **Note assumptions and limitations** — What does this method assume? Where could it mislead?
+   5. **Present the plan to the user and WAIT for confirmation** before proceeding.
+
+   For detailed methodology guidance, see `skills/research-literacy/SKILL.md`.
+   ```
+
+4. **Verification Notice** — Standard disclaimer:
+
+   ```
+   ## ⚠️ 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](https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues).
+   ```
+
+5. **Domain-specific content** — The actual skill logic with:
+   - Key parameters (every number cited with Author, Year — no page numbers)
+   - Decision logic
+   - Common pitfalls
+   - Step-by-step methodology
+
+**Content Quality Rules:**
+- Every numerical parameter must have a citation `(Author, Year)`
+- No page numbers in citations (high hallucination risk)
+- Skill must pass the litmus test: domain-specific, not general programming advice
+- Under 500 lines total
+- If content exceeds 500 lines, split into SKILL.md + `references/` subdirectory
+
+### Step 3 — User Review and Submission Choice
+
+Display the complete generated SKILL.md to the user.
+
+**First, check `gh` CLI availability:**
+
+```bash
+gh auth status 2>&1
+```
+
+**Then present submission options using AskUserQuestion:**
+
+If `gh` is available:
+- **Submit via gh CLI (Recommended)** — Direct submission to GitHub Issues
+- **Open in browser** — Manual submission via web interface
+- **Save locally only** — Save the file without submitting
+- **Request modifications** — Specify what to change
+- **Abort** — Cancel without saving
+
+If `gh` is NOT available:
+- **Open in browser** — Manual submission via web interface
+- **Save locally only** — Save the file without submitting
+- **Request modifications** — Specify what to change
+- **Abort** — Cancel without saving
+
+**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 Issue with the `community-skill` label:
+
+```bash
+gh issue create \
+  --repo "HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills" \
+  --title "[Community Skill] skill-name-here" \
+  --label "community-skill" \
+  --body "ISSUE_BODY_HERE"
+```
+
+**Issue body format:**
+
+```markdown
+## Contributed Skill: `skill-name-here`
+
+### Source
+- **Knowledge source**: [paper / experience / session / other]
+- **Key references**: [papers cited in the skill]
+
+### Contributor Notes
+> [Any additional context from the user about this skill]
+
+### Generated SKILL.md
+
+<details>
+<summary>Click to expand full SKILL.md</summary>
+
+[Full SKILL.md content here]
+
+</details>
+
+---
+*Submitted via the `contribute-skill` meta-skill.*
+```
+
+On success, display the Issue URL to the user:
+```
+✅ Skill submitted successfully!
+🔗 Issue URL: [URL]
+
+The maintainers will review your contribution. Thank you!
+```
+
+On failure, fall back to Option B.
+
+#### Option B: Open in Browser
+
+1. Save the SKILL.md locally to the current directory as `skill-name-here.md`
+
+2. Prepare the issue body and save it as `skill-name-here-issue.md`
+
+3. Open the GitHub Issues page:
+```bash
+xdg-open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues/new?labels=community-skill&title=%5BCommunity%20Skill%5D%20skill-name-here" 2>/dev/null || \
+open "https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues/new?labels=community-skill&title=%5BCommunity%20Skill%5D%20skill-name-here" 2>/dev/null || \
+echo "Please open: https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues/new?labels=community-skill"
+```
+
+4. Inform the user:
+```
+✅ Files saved:
+   - skill-name-here.md (the skill)
+   - skill-name-here-issue.md (issue body to copy)
+
+🌐 Opening GitHub Issues in your browser...
+
+📋 Next steps:
+1. Copy the content from skill-name-here-issue.md
+2. Paste it into the issue body
+3. Submit the issue
+
+The maintainers will review your contribution. Thank you!
+```
+
+#### Option C: Save Locally Only
+
+Save the SKILL.md to the current directory as `skill-name-here.md`:
+
+```
+✅ Skill saved to: skill-name-here.md
+
+You can submit it later by:
+1. Opening https://github.com/HaoxuanLiTHUAI/awesome_cognitive_and_neuroscience_skills/issues/new
+2. Using the label "community-skill"
+3. Copying the skill content into the issue
+```
+
+---
+
+## Litmus Test Enforcement
+
+Before generating the skill, verify each piece of content against the litmus test:
+
+> "Would a competent programmer who has never taken a cognitive science course get this wrong?"
+
+- If YES → Include it (this is domain knowledge)
+- If NO → Exclude it (this is general knowledge)
+
+Flag any borderline items to the user for their decision.

package/skills/01_Meta-Skills/contribute-skills-via-pr/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: "contribute-skills-via-pr"
+description: "Step-by-step guidance for contributing a new skill to the NeuroAIHub/awesome_cognitive_and_neuroscience_skills repository via GitHub Pull Request, including SKILL.md format requirements, quality rules, and PR checklist"
+domain: "community-contribution"
+version: "1.0.0"
+authors:
+  - "Claude (AI-assisted)"
+review_status: "ai-generated"
+---
+
+# Contribute Skills via PR
+
+## Purpose
+
+This skill encodes the complete workflow for contributing a new skill to the [NeuroAIHub/awesome_cognitive_and_neuroscience_skills](https://github.com/NeuroAIHub/awesome_cognitive_and_neuroscience_skills) repository via GitHub Pull Request. It covers SKILL.md format requirements, quality rules enforced by maintainers, the PR submission process, and the no-Git alternative.
+
+## When to Use This Skill
+
+Activate when the user:
+- Wants to contribute a skill to the NeuroAIHub community repository
+- Asks how to submit a PR to `awesome_cognitive_and_neuroscience_skills`
+- Wants to know the SKILL.md format or quality requirements for this repository
+- Asks about the review process or PR checklist for this repo
+
+## Research Planning Protocol
+
+1. **State the contribution goal** — What domain knowledge does the new skill encode? Is it a new skill, an improvement, or a verification?
+2. **Check for overlap** — Confirm the skill does not duplicate an existing one (see overlap checklist below).
+3. **Declare the skill structure** — Outline the sections and key parameters before writing.
+4. **Note quality constraints** — All numerical parameters need citations; no page numbers; under 500 lines.
+5. **Present the plan and WAIT for user confirmation** before writing the SKILL.md.
+
+## Verification Notice
+
+> This skill was generated by AI from direct inspection of the NeuroAIHub/awesome_cognitive_and_neuroscience_skills repository (April 2026). Repository requirements may change — always check the current CONTRIBUTING.md before submitting. If you find errors, please open an issue.
+
+## Step 1: Check for Overlap
+
+Before writing, verify your skill does not duplicate an existing one. Current skills include (41 total):
+
+`eeg-preprocessing-pipeline-guide`, `erp-analysis`, `mne-python-guide`, `fmri-preprocessing-pipeline-guide`, `fmri-glm-analysis-guide`, `fmri-task-design-guide`, `brain-connectivity-modeler`, `neural-decoding-analysis`, `neural-population-analysis-guide`, `calcium-imaging-analysis-guide`, `lesion-symptom-mapping-guide`, `optogenetics-protocol-designer`, `spiking-network-model-builder`, `drift-diffusion-model`, `bayesian-cognitive-model-builder`, `act-r-model-builder`, `evidence-accumulation-selector`, `parameter-recovery-checker`, `signal-detection-analysis`, `cogsci-statistics`, `cogsci-power-analysis`, `cogsci-visualization`, `neuroimaging-power-guide`, `neuroimaging-sample-size-calculator`, `cognitive-paradigm-design`, `eeg-paradigm-designer`, `divergent-thinking-scoring`, `alternative-uses-task-designer`, `creativity-self-efficacy-mediation`, `reading-time-analysis`, `self-paced-reading-designer`, `sentence-stimulus-norming`, `infant-looking-time-designer`, `tom-task-selector`, `neuropsych-battery-selector`, `visual-search-array-generator`, `research-literacy`, `paper-to-skill`, `contribute-skill`, `verify-skill`, `share-case`
+
+## Step 2: Write the SKILL.md
+
+### Required YAML Frontmatter
+
+Skill name may only contain lowercase letters, numbers, and hyphens. The name must match the folder name.
+
+```yaml
+---
+name: "my-skill-name"
+description: "One-sentence summary of the domain knowledge encoded"
+domain: "your-domain"
+version: "1.0.0"
+authors:
+  - "Your Name"
+papers:
+  - "Author et al., Year"
+dependencies:
+  required:
+    - research-literacy
+review_status: "ai-generated"
+---
+```
+
+Mandatory fields: `name`, `description`, `review_status`. All others are recommended.
+
+### Required Sections (in this order)
+
+1. **Purpose** — What domain knowledge this skill encodes and why it is useful
+2. **When to Use** — Trigger conditions that activate this skill
+3. **Research Planning Protocol** — The standard 5-step preamble (copy template below)
+4. **Verification Notice** — The standard AI disclaimer (copy template below)
+5. **Domain-specific content** — The actual skill logic with cited parameters
+
+### Research Planning Protocol Template
+
+```markdown
+## Research Planning Protocol
+
+1. **State the research question** — ...
+2. **Justify the method choice** — ...
+3. **Declare expected outcomes** — ...
+4. **Note assumptions and limitations** — ...
+5. **Present the plan to the user and WAIT for confirmation** before proceeding.
+```
+
+### Verification Notice Template
+
+```markdown
+## 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 at
+> https://github.com/NeuroAIHub/awesome_cognitive_and_neuroscience_skills/issues.
+```
+
+### Quality Rules
+
+| Rule | Requirement |
+|------|-------------|
+| Skill name | Lowercase letters, numbers, and hyphens only. Must match the folder name. e.g., `my-new-skill` |
+| Citations | All numerical parameters must have `(Author, Year)` |
+| No page numbers | Use `(Luck, 2014)` NOT `(Luck, 2014, p. 187)` |
+| Line limit | SKILL.md must be **under 500 lines** |
+| Directory name | kebab-case, must match the `name` field in YAML frontmatter |
+| Commit prefix | `feat:`, `fix:`, `docs:`, or `refactor:` |
+
+## Step 3: Submit via Git PR
+
+```bash
+# 1. Fork on GitHub, then clone your fork
+git clone https://github.com/<your-username>/awesome_cognitive_and_neuroscience_skills.git
+cd awesome_cognitive_and_neuroscience_skills
+
+# 2. Create a feature branch
+git checkout -b feat/<skill-name>
+
+# 3. Create skill directory and add files
+mkdir -p skills/<skill-name>
+# copy your SKILL.md into skills/<skill-name>/SKILL.md
+# optionally: mkdir skills/<skill-name>/references
+
+# 4. Commit and push
+git add skills/<skill-name>/
+git commit -m "feat: add <skill-name> skill for <one-line description>"
+git push origin feat/<skill-name>
+
+# 5. Open PR on GitHub against the master branch
+```
+
+### PR Template Checklist
+
+When opening the PR, all items must be checked:
+
+- [ ] SKILL.md has required YAML frontmatter (`name`, `description`, `review_status`)
+- [ ] Includes Research Planning Protocol section
+- [ ] Includes Verification Notice section
+- [ ] All numerical parameters have `(Author, Year)` citations
+- [ ] Citations do not contain specific page numbers
+- [ ] SKILL.md is under 500 lines
+- [ ] Directory name uses kebab-case
+- [ ] Commit messages use conventional prefixes (`feat:`, `fix:`, `docs:`, etc.)
+
+## Alternative: No-Git Contribution
+
+If you prefer not to use Git, use the `contribute-skill` meta-skill inside Claude Code:
+
+1. Say **"contribute a skill"** in Claude Code
+2. The meta-skill generates a SKILL.md interactively
+3. It submits the skill as a GitHub Issue with the `community-skill` label
+4. Maintainers review and merge on your behalf
+
+## After Submission
+
+Maintainers may request changes such as:
+- Adding missing `(Author, Year)` citations
+- Removing page numbers from citations
+- Reducing line count if over 500
+- Clarifying the Research Planning Protocol or Verification Notice
+
+Use the `verify-skill` meta-skill to self-review your SKILL.md before submitting to catch common issues early.