agentsclimarketplace
Sign in

Mlops collaboration

Skill MLOps-Courses/mlops-coding-skills/mlops-collaboration

Guide to prepare MLOps projects for sharing, collaboration, and community engagement.From its SKILL.md

Install
npx -y skills add MLOps-Courses/mlops-coding-skills --skill mlops-collaboration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 4 commands, including `git tag -a vX.Y.Z` and 3 more.

SKILL.md

2.7 KB, 667 tokens by cl100k_base, as published. Nobody here has run it

MLOps Collaboration

Goal

To transform a private project into a public, collaborative resource by establishing Governance (License, Code of Conduct), Documentation (README, Contributing), Standardization (Templates, Workstations), and Release Management.

Prerequisites

  • Language: Python
  • Platform: GitHub
  • Context: Open sourcing or team collaboration.

Instructions

1. Repository Governance

Set the rules of engagement.

  1. Code of Conduct: Add CODE_OF_CONDUCT.md to foster a safe community.
  2. Protection: Protect the main branch (require PRs, status checks).
  3. Review: Automate preliminary reviews with tools like Gemini Code Assist (.gemini/config.yaml).
  4. Ignore: Comprehensive .gitignore (exclude secrets, data, venvs).

2. Comprehensive Documentation

Make the project usable and understandable.

  1. README.md: The landing page (Badges, Hook, Quickstart).
  2. MkDocs: Use for full documentation sites (API ref, tutorials) when README.md gets too long.
  3. CONTRIBUTING.md: Guide for developers (env setup, PR process, testing standards).
  4. CHANGELOG.md: Generate from Conventional Commits with git-cliff (replaces Commitizen); commit the rendered file.

3. Standardization & Workstations

Eliminate "it works on my machine".

  1. Templates: Use cookiecutter for scaffolding and cruft update to keep projects synced.
  2. Workstations: Add .devcontainer/devcontainer.json.
    • Define Docker image, extensions, and settings.
    • Enable GitHub Codespaces support.

4. Release Management

Ship with confidence.

  1. Versioning: Follow SemVer (MAJOR.MINOR.PATCH) driven by Conventional Commits.
  2. Changelog: Generate with git-cliff from the commit history (replaces Commitizen/Keep-a-Changelog by hand).
  3. Workflows:
    • GitHub Flow: Small teams, continuous delivery (main is stable).
    • Git Flow: Scheduled releases (develop + release branches).
    • Forking: Open source, distributed contributors.
  4. Process: Bump version -> git-cliff changelog -> annotated vX.Y.Z tag (git tag -a vX.Y.Z) -> gh release create vX.Y.Z.

Self-Correction Checklist

  • License: Is a LICENSE file present?
  • Readme: Does README.md have installation instructions?
  • Contributing: Is CONTRIBUTING.md clear?
  • Devcontainer: Does .devcontainer/devcontainer.json exist?
  • SemVer: Are releases semver-tagged (vX.Y.Z) via gh release create?
  • Changelog: Is CHANGELOG.md generated by git-cliff from Conventional Commits?

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.