Skip to content
TrustedSkillsbeta
Back to all skills

Contribution Guidelines

Checked
hack23·vlatest·backend·Apache-2.0

Provides clear, concise guidance on contributing to open-source projects based on community standards and best practices.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add hack23/riksdagsmonitor --skill contribution-guidelines -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hack23

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned hack23/riksdagsmonitor at ea5b63e2f7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 57 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidelines for contributing to open source projects. It helps users understand best practices, including code style, commit message conventions, and how to submit pull requests effectively. The goal is to ensure contributions are well-received and integrated smoothly into existing projects.

When to use it

  • When preparing a patch or feature for an open-source project.
  • To understand the expected workflow for submitting changes.
  • Before creating a new issue or pull request on GitHub or similar platforms.
  • If you're unsure about how to format your code or commit messages.

Key capabilities

  • Provides guidance on code style and formatting.
  • Explains best practices for writing clear and concise commit messages.
  • Outlines the process of submitting pull requests.
  • Offers advice on interacting with project maintainers.

Example prompts

  • "What are some good commit message conventions?"
  • "How do I submit a pull request to this project?"
  • "Can you explain the code style guidelines for this repository?"

Tips & gotchas

This skill assumes familiarity with basic version control concepts (like Git). Reviewing the specific project's documentation in addition to using this skill is always recommended.