Skip to main content
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 for Jira Service Management and Fellow, when those are connected. 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.
The By Squad template gallery
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

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

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

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

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

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 review

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

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

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

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

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

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

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

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 guardrails

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

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

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

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.

​
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. 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

Templates without integration setup carry two controls.

Configure (the cog)

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.

Create (the plus)

Creates 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.
Integration-backed templates show Set up plus a Configure manually cog. Set up first checks that the required provider has an active connection, then 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. Configure manually 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 first and set the levels you actually want, especially if you used the one-click path.