This guide helps you configure this repository as a discoverable Claude Code skills marketplace on GitHub.
Add these topics to your GitHub repository to make it discoverable:
claude-code- Primary discovery topicclaude-skills- Skills marketplace indicatorai-agents- General AI tooling categorypds- NASA Planetary Data System specific
github-api- For GitHub integration (release notes, issues)nasa- Government/space organizationplanetary-science- Domain-specificautomation- Workflow automationdeveloper-tools- Developer productivity
Via GitHub Web UI:
- Go to your repository: https://github.com/NASA-PDS/pds-agent-skills
- Click the ⚙️ gear icon next to "About" (top right)
- Add topics in the "Topics" field
- Click "Save changes"
Via GitHub CLI:
gh repo edit NASA-PDS/pds-agent-skills \
--add-topic claude-code \
--add-topic claude-skills \
--add-topic ai-agents \
--add-topic pds \
--add-topic github-api \
--add-topic nasa \
--add-topic planetary-science \
--add-topic automation \
--add-topic developer-toolsUpdate your repository description to help with search:
Recommended Description:
Claude Code plugin marketplace for NASA PDS workflows - GitHub automation (release notes, issues, PRs) and security scanning (SonarCloud + Dependabot)
Via GitHub CLI:
gh repo edit NASA-PDS/pds-agent-skills \
--description "Claude Code plugin marketplace for NASA PDS workflows - GitHub automation (release notes, issues, PRs) and security scanning (SonarCloud + Dependabot)"Add these to your repository "About" section:
- Website: https://pds.nasa.gov (or your docs site)
- Topics: See above
- Description: See above
Create a social preview image (1280x640px) showing:
- Repository name
- "Claude Code Skills Marketplace"
- Number of skills available
- NASA PDS branding
Upload via: Settings → General → Social preview
Enable these features for better marketplace experience:
- ✅ Enable Issues for skill requests and bug reports
- Add issue templates (see
.github/ISSUE_TEMPLATE/recommendations below)
- Enable Discussions for community Q&A
- Categories: General, Skill Ideas, Help, Show and Tell
- Create a "Skills Roadmap" project board
- Track planned skills and feature requests
- Enable Wiki for extended documentation
- Pages: Getting Started, Skill Development Guide, FAQ
name: 🆕 New Skill Request
description: Suggest a new skill for the PDS Claude Code Skills marketplace
title: "[Skill Request]: "
labels: ["enhancement", "skill-request"]
body:
- type: input
id: skill-name
attributes:
label: Skill Name
description: Proposed name (use gerund form, e.g., "generating-validation-reports")
placeholder: "generating-..."
validations:
required: true
- type: textarea
id: description
attributes:
label: Description
description: What should this skill do? When should it be invoked?
placeholder: "This skill should..."
validations:
required: true
- type: textarea
id: use-cases
attributes:
label: Use Cases
description: Specific scenarios where this skill would be useful
placeholder: "- Use case 1\n- Use case 2"
validations:
required: truename: 🐛 Bug Report
description: Report a bug with an existing skill
title: "[Bug]: "
labels: ["bug"]
body:
- type: dropdown
id: skill
attributes:
label: Which skill?
options:
- generating-release-notes
- creating-pds-issues
- creating-pds-pull-requests
- sonarcloud-security-exporting
- sonarcloud-security-triaging
- sonarcloud-security-updating
- dependabot-alerts-exporting
- dependabot-alerts-triaging
validations:
required: true
- type: textarea
id: what-happened
attributes:
label: What happened?
description: Describe the bug
validations:
required: true- GitHub topics added
- Repository description updated
- README.md "Available Plugins & Skills" section is current
- Badges accurate (plugins count, skills count, license)
- Issue templates created
- CONTRIBUTING.md exists (or created)
- CHANGELOG.md updated
- Social preview image created and uploaded
- Repository starred by team members (increases visibility)
- Share in PDS Engineering Node Slack
- Add to internal documentation
- Include in onboarding materials
- Demo in team meetings
- Blog post on PDS website
- Tweet/social media announcement
- Post in Claude Code Discord/community forums
- Add to awesome-claude-code lists (if they exist)
- Present at conferences (ESIP, AGU, etc.)
- Update skills/plugins count badges when adding new skills
- Keep README.md "Available Plugins & Skills" table in sync
- Update CHANGELOG.md with version history
- Review and respond to issues/PRs promptly
Track marketplace success with:
- GitHub stars
- Repository clones (GitHub Insights → Traffic)
- Issue/discussion activity
- PR contributions from community
Consider these for v2.0:
- GitHub Pages Site - Interactive skill browser with search/filter
- GitHub Actions - Automated skill validation and testing
- Skill Templates - Cookiecutter/scaffolding for new skills
- Version Management - Skill versioning and compatibility matrix
- Usage Analytics - Track which skills are most used (opt-in)
- Skill Dependencies - Define inter-skill dependencies
Questions? Open an issue or contact the PDS Engineering Node team.