> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Agent templates
> Ready-made agents written by Squad, including integration-backed templates with guided setup.
The **By Squad** tab on the Agents page holds agents Squad already wrote, with full instructions, triggers, access, and outputs. Start from one when you want the standing job without writing the brief. Templates that use an integration collect their connection-specific choices before creating the agent.
The same gallery also offers a [workflow](/workflows) for Jira Service Management, Fellow, GitHub, and the app store review sources. Those are ingestion rather than agents, so they have no instructions and no schedule, and their cards read **As it happens** where a template's reads Daily or Weekly. This page is about the agent templates.
Everything on the tab is on offer whether or not you have connected the tool behind it. Click **Set up** on a card whose provider is missing and the modal names the connection it needs and offers **Connect** on the spot. Where signing in is the whole story, you come back to the same card with the modal still open. Jira is the exception. Access to the site is not enough on its own, so connecting ends on the Jira settings page where you choose which spaces Squad watches. The modal says so before you start.
The gallery uses the same toolbar as the agents list. Card grid by default, a toggle for compact rows, plus search, filter, and sort. Filter by **Trigger**, **Cadence**, or **Integration**. Filter **Cadence** to **As it happens** for the workflows alone, or to **Daily** or **Weekly** for the agents.
## Templates
`competitor-tracker`. Watches your competitors and reports meaningful changes to pricing, product, and positioning each day. It keeps one index document of every competitor you track plus a profile per competitor, and records material changes with dates. Daily.
`social-pulse`. A daily read on what people are saying about your product and your space across social channels. It keeps one durable record of recurring themes, sentiment shifts, and the communities worth watching. Passing chatter stays in the daily report. Daily.
`market-research`. Researches your market daily and reports the trends, players, funding, and regulatory shifts that matter, with takeaways. It maintains a market map of segments, key players, and open questions. Daily.
`distribution-opportunities`. Hunts for channels, partnerships, and communities that could put your product in front of more of the right people. It keeps a playbook of every opportunity with reach, effort, the concrete first step, and current status. Daily.
`strategy-consultant`. A weekly strategic review of your goals, feedback, and market position, with candid recommendations. It maintains a working perspective file of durable themes, live hypotheses with evidence for and against, open questions, and a log of past advice and what happened to it. Weekly.
`build-vs-demand`. Compares what shipped against what customers are asking for, and flags where delivery is running ahead of demand or where real demand is going unbuilt. It reads Squad's own knowledge, insights, and goals, so it works best once your delivery record and customer feedback already flow in. It keeps a ledger of each demand theme, its evidence strength, delivery status, related goal, and how the gap is trending. Weekly.
`weekly-shipped-work`. Reviews the 50 most recently updated Linear issues, identifies completed work, maintains a shipped-work knowledge index, and reports what shipped each week. Requires Linear. Read-only.
`stalled-work-watcher`. Reviews the recently updated Linear issue window for explicit blockers and possible progress risks, then produces a concise risk report. It names gaps where the available issue data cannot confirm ownership or inactivity. Requires Linear. Read-only.
`release-readiness-brief`. Summarizes completed work, remaining issues, blockers, and delivery confidence from recent Linear activity. It makes the 50-issue window and lack of project or date filtering explicit. Requires Linear. Read-only.
`recurring-bug-detector`. Finds likely bug themes in recent Linear issues and maintains a product-quality watchlist of recurring risks. Requires Linear. Read-only.
`customer-channel-digest`. Reads selected Slack channels each week, clusters requests, pain points, praise, objections, and open questions, then creates signals and a digest. Requires at least one channel the Squad bot can read. Read-only in Slack.
`escalation-radar`. Reads selected Slack channels daily for urgent customer language, repeated follow-ups, and unresolved questions. It creates signals from direct customer evidence and a ranked escalation report. Requires at least one channel the Squad bot can read. Read-only in Slack.
`sales-objection-tracker`. Reads selected sales or prospect Slack channels weekly, extracts common objections and missing proof points, and creates Squad signals. Requires at least one channel the Squad bot can read. Read-only in Slack.
`prd-evidence-guard`. Watches one shared Notion PRD and compares each change with Squad insights, goals, and knowledge. Requires a Notion page. Read-only.
`research-freshness-monitor`. Watches a shared Notion research page and identifies findings or assumptions that may need re-validation. It maintains a research freshness ledger. Requires a Notion page. Read-only.
`support-request-triage`. Runs when a request is created in selected Jira Service Management spaces, assesses its theme and urgency, and creates signals plus a Squad-side report. Requires at least one monitored space. Read-only in Jira.
`incident-theme-tracker`. Runs for new requests in selected Jira Service Management spaces, groups them into recurring incident themes, and tracks recent urgency and volume in an index. Requires at least one monitored space. Read-only in Jira.
`morning-briefing`. Reports every morning on what moved in the last 24 hours, covering new signals, new insights, and actions completed. It cites the item behind every claim and says so plainly when the night was quiet. No sources or connections needed. Daily.
`weekly-briefing`. Reports every week on the trailing seven days, grouped into themes, with the trend against previous weeks and a watch list of what is forming but not yet worth acting on. No sources or connections needed. Weekly.
Both briefings already run in your workspace. Squad creates them when the workspace is created, so use these cards to rebuild one you deleted or to run a second copy on a different brief.
## What each one produces
Every template generates a report when it runs. Scheduled templates also report on a quiet day or week, giving you a written "nothing moved" rather than silence. Event-backed templates run only when their configured Notion page or Jira request event arrives. Templates that maintain a working knowledge document do so through their instructions and explicit knowledge access.
**Competitor tracker**, **Social pulse**, and **Market research** have **Discover insights** on, so what they read becomes signals that cluster into [insights](/insights). **Distribution opportunities**, **Strategy consultant**, and **Build vs demand review** don't extract signals. Their value is the report, and each keeps a working knowledge document (a playbook, a perspective file, a ledger) it maintains through its instructions and knowledge access.
**Customer-channel digest**, **Escalation radar**, **Sales-objection tracker**, **Support request triage**, and **Incident theme tracker** also discover insights. **Weekly shipped work**, **Recurring bug detector**, **Research freshness monitor**, and **Incident theme tracker** can create or update their working indexes. **Stalled-work watcher** and **Release readiness brief** read Linear alongside Squad context and produce their reports; **PRD guardrails** reads its configured Notion page alongside Squad context.
No template ships with a delivery channel. Add Slack or email afterwards, or up front through Configure for templates that offer it.
## Two ways to start
Every template card carries a cog and one button. The cog is the long way round, the button is the short one.
Opens the New agent form prefilled with the template's name, description, instructions, schedule, and outputs, plus the standard access defaults. Change anything, then create. Take this path to see and set what the agent can reach before it runs.
On a template with nothing to choose, the button reads **Create**. It makes the agent immediately from the template as written, queues its first run, and drops you back on the Agents tab with the new agent already running. Template names are fixed, so creating the same one twice appends a number (`Social pulse 2`) rather than failing.
On an integration-backed template the button reads **Set up** instead, because there is something to choose first. It asks only for the values the template needs: Slack channels, a Notion page, Jira spaces, or no additional scope for Linear. The agent is created only after every required choice is present. If the provider is not connected, the modal connects it for you and picks up where you left off, unless there is a further choice to make on the provider's own settings page. If you started connecting it and stopped, it says so and links you to the half-finished connection instead.
The cog on an integration-backed template opens the regular builder with the template instructions and outputs already filled in. A setup checklist links to the required integration and names the trigger and scope that still need configuring, so you can adjust the standing brief before creating the agent.
On the five research templates, one-click **Create** writes no tools and access levels. Open an agent made this way and every row in **Tools and access** reads as off or None, and the connections list is empty. It still runs. There's a built-in fallback covering the web, your knowledge base, insights, and goals, and the page won't tell you that. Set any level on that page and the fallback stops applying, so only what you set counts. **Build vs demand review** is the exception among the setup-free templates. It writes its own access and keeps the web off. Use **Configure** if you want the access written down from the start.
## After you create one
A template agent is an ordinary agent. Rename it, rewrite its instructions, change its schedule, add triggers, tighten or widen its access, and switch outputs on and off. Nothing about it stays tied to the template.
Open [Tools and access](/agent-tools-access) first and set the levels you actually want, especially if you used the one-click path.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.