Review a plugin or connector

Use this before adding a plugin, connector, skill, or MCP server to a workflow. It helps you see the access involved and the unanswered questions behind a useful-sounding feature.

Prompt template

Help me review [plugin, connector, skill, or MCP server] for [task].

Official documentation or supplied material: [links or excerpts].
Account and environment: [known setup].
Information it would receive: [approved data description].
Actions we need: [read, draft, write, send, delete, or other].

Explain what kind of extension it is and what it adds. Create a review table covering capabilities, permissions, credentials, data destinations, retention, maintenance, costs, revocation, and human approval.

Label each finding as documented, inferred, or unknown. Point to supporting supplied material for documented claims. Identify the most consequential unanswered questions and a narrow read-only test.

Do not assume access from the product name or suggest sharing credentials in a prompt. Do not install or connect anything.

Boundary: Produce only the review and a proposed read-only test plan. Preserve supplied facts, permissions, and constraints; leave source material and access settings unchanged.

Fill in this prompt in the builder

What to supply

  • The extension name and the task it would support.
  • Official material, account setup, and the information it would receive.
  • The exact actions you need, including whether writing or sending is allowed.

Worked example

Illustrative example: the input and result below are invented.

Input

Eli, 28, is reviewing a fictional knowledge connector. Its supplied excerpt says: 'Reads articles in one selected folder. Stores a search index. Administrators can revoke access.' Eli only needs article lookup; retention, index location, and deletion timing aren't stated.

Filled-in prompt

Show the complete prompt
Help me review a fictional knowledge connector for looking up approved help articles.

Official documentation or supplied material: Supplied fictional excerpt: reads articles in one selected folder, stores a search index, and allows administrator revocation.
Account and environment: work account; administrator approval required; not connected.
Information it would receive: approved public help articles in one folder.
Actions we need: read articles only; no write, send, or delete actions.

Explain what kind of extension it is and what it adds. Create a review table covering capabilities, permissions, credentials, data destinations, retention, maintenance, costs, revocation, and human approval.

Label each finding as documented, inferred, or unknown. Point to supporting supplied material for documented claims. Identify the most consequential unanswered questions and a narrow read-only test.

Do not assume access from the product name or suggest sharing credentials in a prompt. Do not install or connect anything.

Boundary: Produce only the review and a proposed read-only test plan. Preserve supplied facts, permissions, and constraints; leave source material and access settings unchanged.

Result

Documented in supplied excerpt: Selected-folder reading, a search index, and administrator revocation.
Unknown: Index location, retention period, deletion after revocation, cost, maintenance owner, and exact authorization scope.
Access boundary: Reading the approved folder only. Any broader permission request needs review.
Questions to resolve before the read-only test: Where is the index stored? What remains after revocation? Can access be limited to the selected folder?
Decision: Resolve the data-destination and revocation gaps before connecting.

What I’d check or correct

I'd check the actual permission screen against the folder restriction. A sentence about revocation doesn't establish when indexed data is deleted, and the review should leave that gap visible.

What to check

  • Permission requests match the actions and information you approved.
  • The result remains a review; it leaves the source material and access settings intact and doesn't install or connect anything.
  • Documented findings have locators, while retention and revocation gaps stay explicit.

Related pages

Sources

Share this page