agentsclimarketplace
Sign in

Office skills review

Skill arih04x/office-skills/.claude/skills/office-skills-review

Review pull requests and local changes for the office-skills repository. Use when validating Office skills, checking SKILL.md frontmatter, reviewing repository structure, or scanning for hardcoded secrets before commit/push.From its SKILL.md

Install
npx -y skills add arih04x/office-skills --skill office-skills-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.8 KB, as published. Nobody here has run it

Office Skills Review

Review changes against this repository's skill packaging rules.

Phase 1: Automated Validation

Run the validator from the repository root:

python .claude/skills/office-skills-review/scripts/validate_skills.py

The script checks:

  • every top-level office-* skill has SKILL.md
  • SKILL.md frontmatter is parseable
  • required fields are present: name, description
  • name matches the skill directory
  • high-confidence hardcoded secrets are not present in tracked-style text files
  • each skill exposes examples/community/{good,corrections,anti-patterns}
  • rendered previews stay under examples/, not assets/previews/
  • local secret files such as config/office-skills.local.env are skipped

All ERROR findings must be fixed before publishing.

Phase 2: Manual Review

After automated checks pass, review the changed files:

  1. Skill boundary: each skill should remain independently usable.
  2. Secret handling: real API keys stay in ignored local files; examples use placeholders.
  3. Cross-platform behavior: Windows paths must have macOS/Linux equivalents when practical.
  4. Asset purpose: examples/previews belong in examples/; only reusable templates, styles, starters, and support resources belong in assets/.
  5. Documentation: .codex/INSTALL.md, README.md, and relevant references should stay in sync.

Read references/structure-rules.md and references/quality-guidelines.md for details.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.