NASA Advanced Multi-Mission Operations System avatar

NASA Advanced Multi-Mission Operations System

Official

@nasa-ammos · NASA

0Followers
|
93Public Repos
|
16Published Skills

Administrator contacts: [email protected] and [email protected]. For AMMOS software tech support, please contact the developers

Skills Distribution
DomainDeveloper To...Project Governance.. (30%)Technical Document.. (30%)Software Lifecycle.. (25%)Security & Vulnera.. (15%)

Agent Skills by NASA Advanced Multi-Mission Operations System

Showing 16 vetted skills indexed across 1 GitHub repositories.

NASA-AMMOSNASA-AMMOS
35

slim-meeting-summary

Convert meeting notes into structured markdown summaries with actionable items.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-project-aware-workspace

Generate a date-organized project workspace with dynamic and static folders.

Official
Intermediate
NASA-AMMOSNASA-AMMOS
35

slim-code-of-conduct

Generate standardized code of conduct and citation templates for projects.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-rebranding

Rebrand SLIM marketplace artifacts across hero, registry, and documentation assets.

Official
Advanced
NASA-AMMOSNASA-AMMOS
35

slim-contributing-guide

Generate comprehensive CONTRIBUTING.md guides for open source projects.

Official
Advanced
NASA-AMMOSNASA-AMMOS
35

slim-changelog

Automates CHANGELOG.md creation and maintenance with Keep a Changelog structure and semantic versioning guidance.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-issue-templates

Generates GitHub issue templates for bugs and feature requests in Markdown and Form formats.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-governance

Provide governance templates with roles and processes for open source projects.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-continuous-testing

Automate testing setup with TESTING.md and pre-commit configurations.

Official
Intermediate
NASA-AMMOSNASA-AMMOS
35

slim-readme

Generate a README.md template with Installation, Usage, Contributing, and License sections.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-license

Apply standard or NASA/JPL software licenses to project repositories.

Official
Basic
NASA-AMMOSNASA-AMMOS
35

slim-skill-creator

Create SLIM-compliant Claude skills with SKILL.md templates and dependency tracking.

Official
Advanced
NASA-AMMOSNASA-AMMOS
35

slim-meeting-agenda

Create structured meeting agendas from MEETINGS.md, TECH.md, and external services.

Official
Intermediate
NASA-AMMOSNASA-AMMOS
35

slim-executive-summary

Generate executive-summary.md from workspace communications and project context.

Official
Intermediate
NASA-AMMOSNASA-AMMOS
35

slim-website-maker

Generate a Docusaurus documentation website from project materials.

Official
Advanced
NASA-AMMOSNASA-AMMOS
35

slim-container-vulnerability-scanning

Automate vulnerability scanning for Docker images and package dependencies with Grype.

Official
Advanced

Frequently Asked Questions About NASA Advanced Multi-Mission Operations System

FAQPage Schema
What specific project management tasks are enabled by these capabilities?

These capabilities enable the generation of standardized project artifacts including issue templates, meeting agendas, executive summaries, and governance documentation. They facilitate consistent project structure through date-organized workspaces and ensure compliance by applying NASA/JPL software licenses and standardized code of conduct templates to repository environments.

Which personas benefit most from these technical resources?

Software engineers, project leads, and open-source maintainers benefit from these resources. They are designed for technical teams requiring rigorous documentation standards, consistent repository governance, and integrated security scanning to maintain high-quality, compliant software deliverables within complex mission-oriented environments.

What are the prerequisites for implementing these project management templates?

Implementation requires a repository environment compatible with Markdown-based documentation and standard version control practices. Users should have existing project context, such as MEETINGS.md or TECH.md files, to populate the generation templates effectively, and ensure Docker environments are configured for vulnerability scanning integration.