report-writing
Create Completion Reports
Teams lose context when completed work is not documented. This skill turns changes, impact, validation, and follow-up tasks into a structured completion report.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "report-writing" from https://skillstore.io/skills/doyajin174-report-writing.md and its manifest at https://skillstore.io/api/skills/doyajin174-report-writing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "report-writing". A refactor renamed a project folder and all validation passed.
Expected outcome:
Report includes a date-based filename, rename reason, affected paths, Before and After comparison, validation summary, and follow-up checklist.
Using "report-writing". A security audit fixed authentication checks and found one follow-up task.
Expected outcome:
Report lists the security change type, modified files, test results, impact scope, and the remaining follow-up item.
Using "report-writing". A documentation update changed setup instructions for a new release.
Expected outcome:
Report explains the documentation scope, changed pages, review status, user impact, and remaining publishing steps.
Security Audit
SafeAll static findings were adjudicated as false positives caused by Markdown fences, inline code spans, and read-only git command examples in SKILL.md. No evidence found for prompt injection, data exfiltration, dynamic execution, or unauthorized network behavior in the skill text.
Risk Factors
⚙️ External commands (27)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/doyajin174-report-writing/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/doyajin174-report-writing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/doyajin174-report-writing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-report-writing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/doyajin174-report-writing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Doyajin174. (2026). report-writing security audit report (audit version 8) [Author version 1.0]. Skillstore. https://skillstore.io/skills/doyajin174-report-writing/audits/8BibTeX citation
@techreport{doyajin174-doyajin174-report-writing-2026,
author = {Doyajin174},
title = {report-writing security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/doyajin174-report-writing/audits/8},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "report-writing security audit report (audit version 8)"
version: "1.0"
type: report
authors:
- name: "Doyajin174"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doyajin174-report-writing/audits/8"
identifiers:
- type: other
value: "skillstore:doyajin174-report-writing:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Record Implementation Outcomes
Create a consistent report after a feature, fix, or refactor is complete.
Prepare Review Handoffs
Summarize changed files, validation results, impact, and remaining follow-up tasks for reviewers.
Document Audit Work
Capture security or quality changes with clear scope, evidence, and verification notes.
Try These Prompts
Create a completion report for this finished task. Include the change reason, changed files, validation results, and follow-up tasks.
Draft a docs/reports report for these changed files. Classify each change type and explain the impact in simple terms.
Write a migration completion report with Before and After sections, direct impact, indirect impact, preserved behavior, and validation evidence.
Create a detailed release handoff report. Include decisions made, alternatives rejected, changed file groups, verification evidence, risks, and next actions.
Best Practices
- Write the report immediately after the task while details are fresh.
- Include actual validation results instead of only saying the work was tested.
- Keep follow-up tasks specific enough for another person to continue the work.
Avoid
- Do not use the report as a replacement for tests or code review.
- Do not omit impact analysis when files or behavior changed across modules.
- Do not list changed files without explaining why each group changed.
Frequently Asked Questions
Does this skill execute shell commands?
Can I change the report folder?
Is this only for code changes?
Does it create test evidence automatically?
Can Claude, Codex, and Claude Code use it?
What makes a good report title?
Developer Details
Author
Doyajin174License
MIT
Author version
v1.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
6 downloads · 263 views
File structure
📄 SKILL.md