From slim-rebranding
Generates code of conduct policies via Contributor Covenant, scientific collaboration guidelines, and CITATION.cff academic citation templates. For open source, research, and academic projects establishing team culture and governance.
npx claudepluginhub nasa-ammos/slim --plugin slim-rebrandingThis skill uses the workspace's default tool permissions.
A code of conduct is essential for establishing standards of interaction within project teams, promoting positive community environments, and providing clear mechanisms for conflict resolution. This skill helps you implement professional code of conduct policies using industry-standard templates that can be customized for your specific project needs.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
A code of conduct is essential for establishing standards of interaction within project teams, promoting positive community environments, and providing clear mechanisms for conflict resolution. This skill helps you implement professional code of conduct policies using industry-standard templates that can be customized for your specific project needs.
The skill provides three specialized templates: the widely-adopted Contributor Covenant for standard projects, a scientific collaboration policy for research environments, and academic citation guidelines for research software projects.
This skill provides three templates that can be used individually or in combination:
Purpose: Standard code of conduct for open source projects and general team collaboration Best for: Most open source projects, community-driven development, general team guidelines Key features: Comprehensive behavior standards, reporting mechanisms, enforcement guidelines
Purpose: Specialized collaboration policy for research environments Best for: Academic research projects, scientific software, publication-oriented teams Key features: Publication ethics, authorship guidelines, research integrity standards
Purpose: Standardized citation file for research software projects Best for: Academic software, research tools, projects requiring scholarly citation Key features: Author metadata, DOI integration, publication references, academic formatting
Before implementing any code of conduct policies, discuss with your team:
Assess project needs:
# Consider your project type:
# - General open source project → Contributor Covenant
# - Research/academic project → Scientific Collaboration + Citation
# - Mixed community → Multiple templates as needed
Gather team consensus:
I will now present the available templates. Please let me know which ones you need for your project:
Option A: Standard Code of Conduct
assets/CODE_OF_CONDUCT.md (Contributor Covenant)Option B: Scientific Collaboration Policy
assets/CODE_OF_COLLAB.mdOption C: Academic Citation File
assets/CITATION.cffOption D: Combination
Which template(s) do you need for your project? Please specify A, B, C, or a combination.
Based on your selection, customize the chosen template(s):
Copy and customize the template:
cp assets/CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md
Required customizations:
[INSERT CONTACT METHOD] with appropriate contact details:
Optional customizations:
Copy and customize the template:
cp assets/CODE_OF_COLLAB.md CODE_OF_COLLAB.md
Key customizations:
Copy and customize the template:
cp assets/CITATION.cff CITATION.cff
Required customizations:
[INSERT PROJECT TITLE]: Your software/project name[INSERT FIRST NAME] and [INSERT LAST NAME]: Author information[INSERT EMAIL]: Primary contact email[INSERT INSTITUTION/ORGANIZATION]: Affiliation[INSERT REPOSITORY URL]: GitHub/GitLab repository URL[INSERT PROJECT ABSTRACT/DESCRIPTION]: Project summary[INSERT KEYWORDS]: Relevant research keywords[INSERT LICENSE]: Your project's license (e.g., Apache-2.0, MIT)[INSERT VERSION]: Current version (e.g., 1.0.0)[INSERT RELEASE DATE]: Release date in YYYY-MM-DD formatOptional customizations:
[INSERT ORCID ID][INSERT DOI]Add this badge to your README.md for visibility:
[](CODE_OF_CONDUCT.md)
Add references to your code of conduct in key locations:
## Code of Conduct
This project follows our [Code of Conduct](CODE_OF_CONDUCT.md). Please read it before contributing.
## Collaboration Guidelines
See our [Collaboration Policy](CODE_OF_COLLAB.md) for research-specific guidelines.
## Citation
If you use this software in your research, please cite it using the information in [CITATION.cff](CITATION.cff).
Reference your conduct policies in CONTRIBUTING.md:
## Community Standards
Before contributing, please review:
- [Code of Conduct](CODE_OF_CONDUCT.md) - Community behavior standards
- [Collaboration Policy](CODE_OF_COLLAB.md) - Research collaboration guidelines
Announce the policy:
Establish enforcement procedures:
Regular review:
For standard projects:
For research projects:
Q: Do I need all three templates? A: No, choose based on your project type. Most projects need only one or two templates.
Q: Can I customize the Contributor Covenant template? A: Yes, but maintain the core principles. Focus on customizing contact information and project-specific details.
Q: How do I handle code of conduct violations? A: Follow your defined procedures. Document incidents, communicate with all parties, and take appropriate action based on severity.
Q: Should I create the citation file even if my project isn't academic? A: If your software might be used in research or academic contexts, a citation file helps users cite your work properly.
Q: How often should I review these policies? A: Review annually or when significant team changes occur. Update contact information immediately when needed.
Q: What if my institution has specific requirements? A: Customize the templates to meet institutional requirements while maintaining the core principles and structure.
Issue: Team resistance to formal conduct policies
Issue: Unclear reporting procedures
Issue: Citation file not recognized by academic databases
Issue: Conflicts between different cultural norms
Issue: Policy enforcement challenges
CODE_OF_CONDUCT.md: Contributor Covenant template with customization placeholdersCODE_OF_COLLAB.md: Scientific collaboration policy templateCITATION.cff: Academic citation file template with comprehensive metadata fields