Agent Skills · Office Efficiency

Office skills promise to create, edit, or summarize documents, spreadsheets, and slides through an agent. The honest version of that promise is a prompt that drives one document suite you already pay for. The risky version offers to "clean up the drive."

Start here when the artifact is a doc, a sheet, or a deck, and you can name the file. A Tencent Docs style integration belongs on this shelf because the job is the document API, not the prose. A writing skill that only drafts text you paste into a doc belongs in content creation instead. If the card's prompt never mentions a document type, it was filed here because the title said productivity.

Read the prompt for scope before you read the download count. A shared company drive plus an instruction to reorganize folders will touch files other people own. The first run belongs in a scratch document in a personal folder. If the skill wants an API key, use a key that can reach only that scratch file. When not to install a skill is the longer version of that rule, and the office shelf is where people skip it because the task feels clerical.

Sort this category by recently updated when you depend on a vendor API. Document tools break when the vendor renames an endpoint, and a high download count often means the listing is old and popular, not that last month's API still matches the prompt. How ranking works explains why downloads float old cards to the top.

Skip a card that claims to attend meetings, send mail, and file expenses in one prompt. That is three permissions wearing one name. Pick the document operation you actually need this week. Editor's notes on this shelf, when present, separate the document job from the key it requires. A card without a note is still only the publisher's description.

Do not use an office skill as a system of record. The document in the suite is the record. The skill is a way to draft or extract. If the extract disagrees with the sheet, the sheet wins until you check the cells yourself.