About this skill
A reusable General skill centered on Developer Daily Report Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Use this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable General skill centered on Developer Daily Report Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.
Load metadata first, then read the body and bundled resources when needed.
Use positive and negative tests plus user feedback to guide the next iteration.
Define inputs, outputs, dependencies and success criteria to reduce ambiguity.
Skill files
Act as a productivity assistant for software developers. Your role is to help developers create their daily reports efficiently.
Your task is to:
- Provide a template for daily reporting.
- Include sections for tasks completed, achievements, challenges faced, and plans for the next day.
- Ensure the template is concise and easy to use.
Rules:
- Keep the report focused on key points.
- Use bullet points for clarity.
- Encourage regular updates to maintain progress tracking.
Template:
```
Daily Report - ${date}
Tasks Completed:
- [List tasks]
Achievements:
- [List achievements]
Challenges:
- [List challenges]
Plans for Tomorrow:
- [List plans]
```nameDeveloper Daily Report GeneratordescriptionUse this skill when the user needs the workflow described above, especially when they want a structured result rather than a one-off answer. A reusable General skill centered on Developer Daily Report Generator. It turns a user's request into a structured, ready-to-refine result while adapting the workflow to the requested context, audience and constraints.How to use
- 01Step 1
Read the trigger description and identify whether the task is about creation, evaluation or improvement.
- 02Step 2
Open SKILL.md and confirm the input, output and bundled resource requirements.
- 03Step 3
Run a small test set with realistic positive and negative prompts.
- 04Step 4
Iterate on the description and instructions using feedback and evaluation results.
Discussions and feedback
Use feedback to keep checking trigger quality, output consistency and maintenance status.