agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/commenting-content/SKILL.md

commenting-content

Skill95 starsChanged 6 days agoMITView on GitHub

Analyzes a .docx or .pptx file, researches the topic using internal documents, emails, Microsoft Teams messages, and web sources, then adds native comments throughout the file authored by "Copilot Studio AI" — without modifying the original content.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill is activated:

    line 8
  2. Distinctive:

    Check the file extension of the attached document.

    line 10
  3. Very specific:

    If .docx → follow the instructions in REFERENCE-DOCX.md

    line 11
  4. Very specific:

    If any other format → ask the user to convert to .docx or .pptx first.

    line 13
  5. Distinctive:

    Never modify the original document content — add comments only.

    line 19
  6. Distinctive:

    Only comment where it genuinely helps — do not comment on every sentence.

    line 22
  7. Distinctive:

    If multiple files are attached, process them one at a time and produce a separate summary for each.

    line 42
  8. Distinctive:

    If the file type is ambiguous, ask the user to confirm before proceeding.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Comment Content

When this skill is activated:

  1. Check the file extension of the attached document.
    • If .docx → follow the instructions in REFERENCE-DOCX.md
    • If .pptx → follow the instructions in REFERENCE-PPTX.md
    • If any other format → ask the user to convert to .docx or .pptx first.
  2. Execute the full commenting workflow defined in the appropriate reference file.
  3. Return the updated file with native comments embedded and a short chat summary of findings.

Guidelines

  • Never modify the original document content — add comments only.
  • Set the comment author to Copilot Studio AI on every comment added.
  • Research using any available sources: internal documents, emails, Microsoft Teams messages, approved knowledge sources, and web research tools.
  • Only comment where it genuinely helps — do not comment on every sentence.
  • The chat summary must include: comment count, main research findings, and top 1–3 priority issues for the author to review.

Reference Files

  • REFERENCE-DOCX.md — Word document commenting instructions
  • REFERENCE-PPTX.md — PowerPoint presentation commenting instructions

Examples

Example 1: Word document

  • User request: "Add research comments to this report." (attaches report.docx)
  • Expected behavior: Detect .docx, follow REFERENCE-DOCX.md, return commented .docx with summary.

Example 2: PowerPoint presentation

  • User request: "Review this deck and add comments." (attaches deck.pptx)
  • Expected behavior: Detect .pptx, follow REFERENCE-PPTX.md, return commented .pptx with summary.

Notes

  • If multiple files are attached, process them one at a time and produce a separate summary for each.
  • If the file type is ambiguous, ask the user to confirm before proceeding.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free