원클릭으로
slim-issue-templates
Add standardized GitHub issue templates for bug reports and feature requests
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Add standardized GitHub issue templates for bug reports and feature requests
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Add badges to a repository, README, or document. Ships with authorship badges (100% Human Made, AI-assisted, AI-generated, AI-autonomous) and the SLIM Best Practices badge, and is extensible to any badge. Use when a user wants to add, choose, or generate a badge for a project or document.
Launch your own customized best-practices marketplace by rebranding the slim-framework. Prompts the user for project name, logo, organization, and branding, then clones a fresh copy of the NASA-AMMOS/slim-framework repository and customizes that clone — without modifying the repository this skill is run from. Use when you want to stand up your own marketplace website based on the framework.
Sets up a folder based project-aware workspace area on local disk with date-organized dynamic folders for project-aware skill execution and a static folder for relevant information about a project such as personnel, project background, meeting information, products, repos etc. This skill is a foundation skill that sets up structures that allow other AI skills to operate within a project-aware workspace with automatic date-based folder management. For example, skills such as generating executive summaries, writing meeting notes, writing meeting agendas or other skills that involve working with third-party services to coordinate complex behaviors can benefit from the skill.
Meta-skill for creating and integrating new Claude skills into the SLIM marketplace with dependency tracking and automated registry updates. Use when users want to create custom skills, develop specialized workflows, build skill templates, add new capabilities to SLIM, or integrate skills with marketplace infrastructure.
Comprehensive workflow for rebranding SLIM-based Docusaurus websites for domain-specific projects. Handles hero customization, registry imports from external SLIM instances, page template generation, and complete website configuration. Creates customized SLIM forks with domain-specific branding, marketplace entries, and documentation. Includes detailed plan templates and step-by-step guides with git workflow and iterative build testing.
Autonomous website generator skill for creating customized Docusaurus documentation websites. Analyzes project content, generates intelligent website structure, and validates changes with iterative build testing until successful. Creates git branch and commits with clear messages. Auto-detects project type and customizes accordingly. Use when generating project documentation websites, creating content-driven sites, or automating website creation with build validation.
| name | slim-issue-templates |
| description | Add standardized GitHub issue templates for bug reports and feature requests |
Helps development teams keep the language of bug reports, feature requests, and other types of issues readable and consistent. This skill provides both traditional Markdown templates and modern GitHub Form templates.
bug_report.md): Traditional freeform template with guidancebug_report.yml): Structured form with required fieldsnew_feature.md): Freeform template for feature proposalsnew_feature.yml): Structured form for feature requestsCheck if issue templates already exist:
ls -la .github/ISSUE_TEMPLATE/
If templates exist, ask the user if they want to replace them or keep them.
Ask the user which format they prefer:
Recommendation: GitHub Forms (.yml) provide better structure and validation, reducing incomplete reports.
Create the .github/ISSUE_TEMPLATE/ directory if it doesn't exist:
mkdir -p .github/ISSUE_TEMPLATE
Based on the user's choice, copy the appropriate templates:
For Markdown templates:
cp assets/bug_report.md .github/ISSUE_TEMPLATE/
cp assets/new_feature.md .github/ISSUE_TEMPLATE/
For GitHub Forms:
cp assets/bug_report.yml .github/ISSUE_TEMPLATE/
cp assets/new_feature.yml .github/ISSUE_TEMPLATE/
For both:
cp assets/*.md .github/ISSUE_TEMPLATE/
cp assets/*.yml .github/ISSUE_TEMPLATE/
The templates can be customized to fit the project:
Advantages:
Disadvantages:
Advantages:
Disadvantages:
Edit the .md files to:
Edit the .yml files to:
Example field types:
- type: input # Single-line text
- type: textarea # Multi-line text
- type: dropdown # Select from options
- type: checkboxes # Multiple selection
bug_report.md: Markdown bug report templatebug_report.yml: GitHub Form bug report templatenew_feature.md: Markdown feature request templatenew_feature.yml: GitHub Form feature request template