You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
---description: Image optimization skill for web and documentation assets---# Image Optimize Skill## Capabilities- Compress PNG/JPEG images
- Convert to WebP format
- Batch process directories
## Usage[Instructions for invoking the skill]## Tools Required- ImageMagick or sharp (Node.js)
Acceptance Criteria
New skill directory created at .github/skills/<skill-name>/
SKILL.md follows conventions from video-to-gif
Skill provides practical value for documentation or development workflows
This is a structured documentation task using the task-implementor workflow. Although SKILL.md
files share some structural similarities with prompt artifacts, they are developer-facing
documentation, so the standard task-implementor workflow applies.
#file:.github/instructions/writing-style.instructions.md (voice and tone)
Steps
Type /clear to start a fresh context.
Attach or open the files listed above.
Copy and run this prompt:
/task-research topic="designing a second skill package for the HVE Core skills library"
Research what a second skill package should contain and how it should be structured.
Investigate:
1. The video-to-gif SKILL.md structure in detail (frontmatter, sections, script references,
platform-specific content, parameter tables, troubleshooting)
2. The skills authoring guide (docs/contributing/skills.md) for required sections and conventions
3. The three proposed options (image-optimize, code-screenshot, mermaid-render) and which
provides the most practical value for documentation workflows
4. What prerequisite tools each option requires and their cross-platform availability
5. How skills are discovered and invoked by users (the description frontmatter field)
6. Whether the skill needs accompanying scripts, examples, and assets directories
7. The prompt-builder quality criteria and how they apply to SKILL.md files
Output: Research document at .copilot-tracking/research/{{YYYY-MM-DD}}-second-skill-research.md
Phase 2: Plan
Source Material
Research document from Phase 1
Steps
Type /clear to start a fresh context.
Open the research document from Phase 1.
Copy and run this prompt:
/task-plan
Create an implementation plan for the second skill package. The plan should specify
the selected skill topic, the SKILL.md structure (matching video-to-gif conventions),
any required scripts or examples, and the directory layout under .github/skills/.
Output: Plan at .copilot-tracking/plans/ and details at .copilot-tracking/details/
Phase 3: Implement
Source Material
Plan from Phase 2
Steps
Type /clear to start a fresh context.
Open the plan document from Phase 2.
Copy and run this prompt:
/task-implement
Implement the second skill package following the plan. Create the SKILL.md file
with proper frontmatter, all required sections, and any supporting scripts or
examples. Follow the conventions established by the video-to-gif skill.
Output: New skill directory and files, changes log at .copilot-tracking/changes/
Phase 4: Review
Source Material
Plan from Phase 2
Changes log from Phase 3
Steps
Type /clear to start a fresh context.
Open the plan and changes log.
Copy and run this prompt:
/task-review
Review the second skill package implementation. Run these validation commands:
- npm run lint:md (markdown linting)
- npm run lint:frontmatter (frontmatter validation)
Verify the SKILL.md follows the video-to-gif pattern, has proper frontmatter,
covers all required sections from docs/contributing/skills.md, and provides
practical value for documentation or development workflows.
Output: Review log at .copilot-tracking/reviews/
After Review
Pass: All criteria met. Create a PR referencing this issue.
Iterate: Review found issues. Run /clear, return to Phase 3 with the review feedback.
Escalate: Fundamental design issue discovered. Run /clear, return to Phase 1 to research the gap.
Authoring Standards
SKILL.md frontmatter includes name: and description: fields
Description field ends with "- Brought to you by microsoft/hve-core"
Use "you" for instructional content
Guidance style: "Consider", "Prefer", "Use" over command style
No em dashes, no bolded-prefix list items
Platform-specific prerequisites documented per OS
Success Criteria
New skill directory exists at .github/skills/<skill-name>/
SKILL.md follows the video-to-gif structure and conventions
Frontmatter includes required name: and description: fields
Skill provides practical value for documentation or development workflows
Summary
The
.github/skills/directory currently contains only one skill package (video-to-gif). Adding a second skill would:Current State
Proposed Solution
Add a second skill package. Suggested candidates (choose one):
Option A:
image-optimizeOption B:
code-screenshotOption C:
mermaid-renderRecommended:
image-optimizeMost broadly useful and aligns with documentation workflows already in the codebase.
Example structure
SKILL.md content
Acceptance Criteria
.github/skills/<skill-name>/References
.github/skills/video-to-gif/SKILL.mdHow to Build This
This is a structured documentation task using the task-implementor workflow. Although SKILL.md
files share some structural similarities with prompt artifacts, they are developer-facing
documentation, so the standard task-implementor workflow applies.
Workflow:
/task-research→/task-plan→/task-implement→/task-reviewTip
Between each phase, type
/clearor start a new chat to reset context.Phase 1: Research
Source Material
#file:.github/skills/video-to-gif/SKILL.md(exemplar skill package)#file:docs/contributing/skills.md(skills authoring guide)#file:.github/instructions/prompt-builder.instructions.md(artifact quality criteria)#file:.github/instructions/writing-style.instructions.md(voice and tone)Steps
/clearto start a fresh context.Output: Research document at
.copilot-tracking/research/{{YYYY-MM-DD}}-second-skill-research.mdPhase 2: Plan
Source Material
Steps
/clearto start a fresh context.Output: Plan at
.copilot-tracking/plans/and details at.copilot-tracking/details/Phase 3: Implement
Source Material
Steps
/clearto start a fresh context.Output: New skill directory and files, changes log at
.copilot-tracking/changes/Phase 4: Review
Source Material
Steps
/clearto start a fresh context.Output: Review log at
.copilot-tracking/reviews/After Review
/clear, return to Phase 3 with the review feedback./clear, return to Phase 1 to research the gap.Authoring Standards
name:anddescription:fieldsSuccess Criteria
.github/skills/<skill-name>/name:anddescription:fieldsnpm run lint:mdpassesnpm run lint:frontmatterpasses