Skip to main content
Glama
chiruu12

oss-skills-mcp

by chiruu12
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_skillsA

List the bundled OSS contribution skills with their descriptions.

get_skillA

Return the full content of a skill by name, e.g. "oss-find-issue".

Prompts

Interactive templates invoked by user choice

NameDescription
oss-contributeResearch an issue deeply and present all context to the user - but the user writes the code. The LLM investigates code paths, finds relevant files, explains patterns, and identifies constraints. The user thinks through the approach and implements it. Use when ready to start working on an issue after oss-prep-to-contribute.
oss-debug-ciDebug CI failures in unfamiliar repo pipelines. Reads CI configs, fetches failure logs, classifies the failure type, and guides the user through diagnosing and fixing the issue. Use when CI fails on your PR in an OSS repo, when you don't understand a CI error, or when debugging GitHub Actions/CircleCI/other CI systems. Not for setting up CI from scratch — this is for debugging existing pipelines.
oss-evaluate-repoEvaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.
oss-explore-repoGuided codebase exploration for understanding a repo's architecture, patterns, and domain language before contributing. Not issue-specific - builds general understanding. Use when exploring a new repo, wanting to understand how a project works, or preparing to become a regular contributor.
oss-find-issueFind unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues.
oss-find-real-issuesFind actual code issues in a repo that aren't listed in GitHub issues - missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available.
oss-learn-stackLearn unfamiliar technologies used in a repo by studying how the repo actually uses them. Finds patterns, explains concepts in context, and points to examples in the codebase. Use when a repo uses frameworks, languages, or patterns you haven't worked with before.
oss-post-prHandle PR review feedback - understand reviewer comments, research their concerns, and help the user address them. The LLM explains what reviewers want and why; the user decides how to respond and writes the code. Use when you receive review comments on a submitted PR.
oss-prep-to-contributePrepare to contribute to an open source repo. Reads all contribution docs, checks eligibility, assesses the user's knowledge gaps, and fills them before coding starts. Use after finding an issue with oss-find-issue, or when starting work on any OSS repo.
oss-review-prsReview other contributors' PRs to learn the codebase and build maintainer trust. Guides structured diff reading, helps formulate review comments, and teaches how to distinguish blocking issues from nits. Use when you want to learn a codebase by reviewing PRs, build trust with maintainers before contributing code, or practice code review on OSS repos. Not for reviewing your own PR — use oss-submit-pr for that.
oss-second-contributionPlan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-issue → oss-contribute chain for that.
oss-setup-dev-envSet up a complete development environment for an unfamiliar OSS repo. Handles dependency installation, building, running tests, and configuring dev tooling. Use when cloning a new OSS repo and setting up for development, when the repo's setup instructions don't work, or when you need to debug environment issues. Not for setting up your own project — this is for getting someone else's repo running.
oss-submit-prSubmit a pull request following the repo's contribution guidelines. Reviews the diff, checks for common rejection reasons, and helps the user write their own PR description. The LLM reviews - the user writes. Use when implementation is complete and tests pass.
oss-write-docsContribute documentation improvements to an OSS repo. Identifies doc gaps, studies the docs system, and verifies accuracy against source code. Use when contributing documentation to an open source project, fixing outdated setup instructions, adding missing API docs, or improving README clarity. Not for writing docs for your own project — this is for contributing docs to someone else's repo.
oss-write-testsWrite tests for untested OSS code as a standalone contribution. Identifies coverage gaps, studies the repo's test conventions, and guides the user through writing tests that match existing patterns. Use when contributing tests to an open source repo, looking for a low-risk first contribution, or improving test coverage. Not for writing tests alongside a bug fix — use oss-contribute for that.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chiruu12/oss-skills-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server