Tool Permission Matrix and Function Spec for a Tool-Using Agent
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
217 prompts
Prompts written for Claude, Anthropic's assistant. Claude handles long inputs well, so many of these prompts ask you to paste a whole document, transcript or code excerpt and then structure the answer around it.
217 results · page 2 of 10
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
Designs verification checks, error handling, and a self-correction loop for an agent task before it runs, based on likely failure modes.
Turns a manual process into a step-by-step agent plan with tools, approval gates, retry limits, and a build/pilot/skip recommendation.
Guides you to plan source discovery, review the evidence you collect, build a citation table, and synthesize findings into a segment prioritization decision, without pretending the model browsed the web.
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.
Turns your product facts, customer evidence, and competitor notes into a tested positioning statement, messaging hierarchy, and proof-gap list so a marketing team can decide what to say and what to validate first.
Guides a source-backed evaluation of software or service vendors against weighted criteria. Ends with a decision memo covering risks, open questions, and verification steps before purchase.
Tests a specific claim or statistic against primary and peer-reviewed sources. Produces an evidence grid, a contradiction log, and a calibrated confidence rating with explicit unknowns.
Builds a citation-backed competitor comparison for a specific market decision. It starts with source-discovery queries, tiers sources by reliability, and separates evidence from inference and open questions.
Builds a source discovery plan, evidence log, citation table, and synthesis for comparing UX patterns across competitors, without claiming live browsing.
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Audits a user flow from screenshots or descriptions and returns an evidence-labeled issue table plus a fix-now, next, defer plan for a sprint decision.
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
Turns an error report, stack trace, and logs into ranked root-cause hypotheses. Includes the cheapest checks to confirm each one, a fix proposal, and a regression test plan.
Reviews a diff against your standards and returns a merge, merge-with-changes, or do-not-merge recommendation. Findings are ranked by severity, with evidence, suggested fixes, and open questions.
Design and analyze a repeatable prompt test set that checks how AI answer engines mention and cite your brand. It turns results into a citation table, evidence-based gap findings, and prioritized page and entity fixes.
Build a topic cluster from a keyword list and existing content, then rank which cluster and pages to create first. It includes a keyword-to-page mapping table, internal link rules, and cannibalization risks.
Create a writer-ready content brief from SERP observations you supply. It covers intent, required sections, evidence gaps, and a go or no-go call on whether the page is worth producing.
Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.
A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.
Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.
Turns product facts, audience insight, and competitor context into a positioning statement, messaging hierarchy, and proof map so a team can approve one launch angle.
Converts pasted monthly KPI results and targets into a variance analysis, driver hypotheses, and prioritized actions that a leadership team can decide on in one meeting.
Put the documents first and the prompt after them. Anthropic's prompting guide suggests wrapping each document in tags such as <document> so Claude keeps the sources apart.
Yes. Paste it into the project instructions and every chat in that project starts from it. Fill its blanks with the details that stay the same from chat to chat.
No. These are for the Claude apps and the API. For work inside a code repository, where the agent reads files and runs commands, use the Claude Code prompts.