How do I install the Team Collaboration skill?

Run npx skillmds@latest add tomevault-io/team-collaboration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Team Collaboration safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Team Collaboration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Team Collaboration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Team Collaboration?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Team Collaboration by tomevault-io — Agent Skill

Name: Team Collaboration
Author: tomevault-io

File contents

Collaboration & Open Source Contribution

Building software is usually a team effort. Strong collaboration skills – communicating with team members, reviewing each other’s code, and following shared conventions – are essential. Many developers also participate in open-source projects to share knowledge and improve their skills. Contributing to open source is recommended for new developers to gain experience and visibility. Ultimately, being able to work well with others (often asynchronously, across different time zones or via platforms like GitHub) is a key developer superpower.

Examples

Participating in code review: reviewing a colleague’s pull request and providing constructive feedback, as well as responding to feedback on your own code.
Contributing a bug fix or new feature to an open-source project, following the project’s contribution guidelines and coding style.

Guidelines

Code Review Mastery: Engage in code reviews regularly. Read others’ code and provide helpful suggestions, and incorporate feedback from reviewers on your code. For example, if reviewers suggest a function be split for clarity, be willing to refactor. Code review culture leads to better code quality and knowledge transfer.
Open Source Engagement: Consider contributing to open-source projects or internal company repositories. This exposes you to large-scale codebases and different perspectives. It’s also a great way to demonstrate skills. Always follow the project’s contribution guidelines when submitting changes.
Team Communication: Maintain clear and professional communication with team members. Document decisions, update project artifacts, and respect established team conventions. By aligning with team processes, you build trust and velocity in development.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: team-collaborationdescription: Working effectively with others in coding projects – including code reviews, clear communication, and contributing to shared or open-source codebases. Use when this capability is needed.---# Collaboration & Open Source ContributionBuilding software is usually a team effort. Strong collaboration skills – communicating with team members, reviewing each other’s code, and following shared conventions – are essential. Many developers also participate in open-source projects to share knowledge and improve their skills. Contributing to open source is recommended for new developers to gain experience and visibility. Ultimately, being able to work well with others (often asynchronously, across different time zones or via platforms like GitHub) is a key developer superpower.## Examples- Participating in code review: reviewing a colleague’s pull request and providing constructive feedback, as well as responding to feedback on your own code.- Contributing a bug fix or new feature to an open-source project, following the project’s contribution guidelines and coding style.## Guidelines- **Code Review Mastery:** Engage in code reviews regularly. Read others’ code and provide helpful suggestions, and incorporate feedback from reviewers on your code. For example, if reviewers suggest a function be split for clarity, be willing to refactor. Code review culture leads to better code quality and knowledge transfer.- **Open Source Engagement:** Consider contributing to open-source projects or internal company repositories. This exposes you to large-scale codebases and different perspectives. It’s also a great way to demonstrate skills. Always follow the project’s contribution guidelines when submitting changes.- **Team Communication:** Maintain clear and professional communication with team members. Document decisions, update project artifacts, and respect established team conventions. By aligning with team processes, you build trust and velocity in development.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/baz-scm) — claim your Tome and manage your conversions.

Frequently asked questions

Team Collaboration