Name: office-productivity
Rating: 51.2 (1 reviews)
Author: administrakt0r

office-productivity

Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/office-productivity/SKILL.md

The canonical home for this skill is office-productivity in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured but repetitive router listing skills and abstract steps across seven phases, with terse copy-paste invocation prompts but no executable code, no integrated validation for its batch/destructive operations, and no progressive disclosure via bundle files.

Suggestions

Add concrete executable examples or commands for at least the common cases (e.g., a headless LibreOffice conversion command) instead of only abstract action lists.

Insert explicit validation checkpoints into the batch and conversion phases (e.g., 'verify converted file opens; re-run on failure') to lift workflow clarity above the batch-operation cap.

Move per-skill detail into reference files under references/ and link to them one level deep, rather than inlining all phases in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is terse bullet/numbered lists with no concept-explanation padding Claude already knows, fitting 'efficient; minor instances that could be trimmed'; the repeated 7-phase template is structural repetition rather than verbose over-explanation, keeping it below 5.	4 / 5
Actionability	Copy-Paste Prompts ('Use @libreoffice-writer to create ODT documents') give some concrete invocations, but the Actions lists ('Design document template', 'Apply formatting') are abstract with no executable code or commands, matching 'some concrete guidance but incomplete' rather than 4's mostly-executable bar.	3 / 5
Workflow Clarity	Seven phases have numbered sequences, but batch/destructive operations (Phase 4 'Batch process files', Phase 5 generate-and-distribute) lack inline validation; the loose Quality Gates checklist is not integrated as checkpoints, so per the batch-operations cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and everything is inlined in one monolithic file with phase headers — some structure but content that could be split is inline and no external references are signaled, matching the 3 anchor rather than 4.	3 / 5
	Total	13 / 20 Passed

Description

55%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description concretely states what the workflow covers across office formats but lacks any explicit trigger/usage guidance, capping completeness, and is broad enough to conflict with the very skills it aggregates.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., creating .docx/.xlsx/.pptx files, converting formats, mail merge).

Include file extensions and synonyms (.docx, .xlsx, .pptx, .odt, .ods) so the trigger keywords match what users actually say.

Narrow or clarify the niche (e.g., 'orchestrates multi-format office document workflows') to reduce overlap with the individual skills it routes to.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats') with minor gaps in coverage (e.g., conversion, mail merge absent), matching the 'several specific actions; minor gaps' anchor rather than 5's comprehensive coverage or 3's 1-2 actions.	4 / 5
Completeness	Clearly states 'what' the workflow does but has no 'Use when...' clause or equivalent trigger guidance, so per the missing-trigger cap it cannot exceed 3; it is not a 2 because the 'what' is concrete, not vague.	3 / 5
Trigger Term Quality	Contains relevant terms ('document creation', 'spreadsheet automation', 'LibreOffice', 'Microsoft Office') but omits common synonyms and all file extensions (.docx, .xlsx, .pptx, .odt), fitting 'some relevant keywords but missing common variations' rather than 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	Naming LibreOffice/Microsoft Office gives some specificity, but as a broad bundle spanning documents, spreadsheets, and presentations it overlaps heavily with the many individual skills it routes to, matching 'somewhat specific but could still overlap with similar skills.'	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/office-productivity/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.