Individual skill
work-status-reporting
Use when preparing, reviewing, or correcting weekly, daily, periodic, or client-facing work status reports where finished work, moderation, diagnosis-only progress, unverified repairs, automation/system activity, and in-progress items must not be double-counted or overstated.
plugins/nebelov/yandex-direct-for-all/skills/work-status-reporting/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,531
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,279 bytesSKILL.mdcore · 2,279 bytesagents/openai.yamlasset · 271 bytes
Read excerpt
# Work Status Reporting
Use this skill for weekly or periodic status reports, especially when the user
needs a truthful summary of many operational tasks, campaigns, automations, or
client deliverables.
## Status Separation
Before writing the report, classify each item by evidence-backed state:
- `finished`: the requested user-visible result was completed and verified;
- `waiting_external`: submitted, sent, or in moderation, but not yet accepted or
live;
- `diagnosis_only`: investigation or root-cause work happened without a verified