Overview
Copy any prompt or skill below into your AI tool. Replace everything in [square brackets] with your own details, for example your Representatives' names, stores, forms, date ranges and targets. Make sure Repsly is connected and turned on in the chat (see Repsly MCP Beta: How to Connect).
Prompts are one-off questions. Skills are reusable instructions for a task you do every week, like a Monday briefing or 1:1 prep. You fill in your setup once and reuse it.
Starter prompts
Tip: you can ask your AI tools to build you a dashboard answering as many of these (or other) prompts you’d like to see answered.
Weekly check-in
"In Repsly, give me my weekly briefing: this week's visit compliance vs last week, which Representatives have [2] or more missed visits, and what's still scheduled for the rest of the week. Keep it to 5 bullets."
"In Repsly, how did visit compliance for [October 1-31] compare to [September 1-30]? Show done, missed and the compliance rate for each."
Missed visits
"In Repsly, list every missed visit in [territory] from [start date] to [end date], with the Representative, store and tasks that weren't done. If the list is partial, tell me the total."
"In Repsly, show me every visit [Representative] missed in the last [2 weeks], and what's on their schedule next week."
Upcoming schedule
"In Repsly, what's on [Representative]'s schedule [next week]? Group it by day with the store, time and assigned tasks. For visits with no set time, say 'any time'."
"In Repsly, which visits are scheduled at [store name or code] in the next [30 days], and who's doing them?"
Completed visits and time in store
"In Repsly, how long did [Representative] spend in each store [this week]? Show the total and average time in store, and flag visits under [10] minutes or over [3] hours."
"In Repsly, did [Representative] check in on time for their scheduled visits [yesterday]? Flag anything more than [15] minutes late."
"In Repsly, which completed visits [yesterday] were unplanned, with no schedule behind them?"
Forms
- "In Repsly, how many forms came in per form [last month], compared with the number of completed visits?"
- "In Repsly, who submitted the [form name] form [last week], and at which stores?"
- "In Repsly, which forms did [Representative] submit at [store] in the last [30 days]?"
- "In Repsly, what did Representatives report in the [form name] form [last week]? Summarize the answers per question and flag anything that stands out."
- "In Repsly, which stores answered [No] to [question] in the [form name] form [this month], and who submitted it?"
- "In Repsly, using the [form name] answers from [last month], count how many times each Representative selected each option for [question], for example which categories they didn't complete."
Targets and pacing
"Our target is [25] completed visits per Representative per week. In Repsly, how is each Representative in [territory or my team] pacing this week? Show done, still scheduled, missed, and whether they'll hit the target."
Reports and sharing
"In Repsly, build me a one-page visit dashboard for [last week]: compliance vs the week before, visits done and missed per Representative, and form submissions per form. Show the date range and say where the data was partial."
"Turn this into a short weekly update for [my regional Admins / our client]: 3 highlights and 3 follow-ups, in plain language."
Checking an answer
"Which Repsly tools and date ranges did you use for that answer? Was any list partial?"
Repsly data rules (paste once)
Paste this into your AI tool's custom or project instructions (Claude Project instructions, ChatGPT custom instructions, a Gemini Gem or your Copilot agent's instructions), or at the start of a chat. It keeps answers honest about what Repsly can and can't tell you. Every skill below already includes it.
- Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data.
- Repsly doesn't record why a visit was missed. Never give a reason unless I provide one.
- Always state the date range you used. Weeks run [Monday to Sunday].
- List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool.
- When a name matches more than one Representative, store or form, ask me which one.
- Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone.
- If a tool says the data isn't available for my access level, say so and carry on with the rest.
- Targets, quotas and goals come from me, not Repsly. Label them as mine.Skills
Skill | Use it for |
|---|---|
Weekly field briefing | Monday check-in: compliance vs last week, at-risk Representatives, missed visits, what's left this week |
Store visit check | Before a client or retailer call: recent visits at one store, missed visits, forms, next visit |
Form submission tracker | Submissions per form vs completed visits, and who or which stores are behind |
Form answers summary | What Representatives answered on a form: answer counts per question, multi-select roll-ups, and the stores or Representatives that stand out |
Visit pacing vs target | Each Representative against your own visit targets for the week or month |
How to use a skill
Copy the skill text and fill in the Your setup section. Leave the rest as is.
Use it in one of these ways:
Any AI tool: paste it at the start of a new chat, then ask, for example "Run my weekly field briefing."
Claude, saved as a skill: upload the instructions under Customize → Skills → + → Create skill → Upload a skill. Edit your setup first. Claude then uses it on its own whenever you ask for that task.
Saved instructions: paste it into a Claude Project, a ChatGPT Project, a Gemini Gem or a Copilot agent's instructions, with Repsly connected.
Weekly field briefing
Try: "Run my weekly field briefing." / "Weekly briefing for last week instead."
---
name: repsly-weekly-field-briefing
description: Weekly field briefing from Repsly - visit compliance this week vs last week, Representatives at risk, missed visits and what's still scheduled. Use when I ask for my weekly or Monday briefing, a field status update, or how the team did this week in Repsly.
---
# Repsly weekly field briefing
## Your setup (edit this)
- Team or company name: [e.g. Acme Foods, East team]
- Who reads this: [me / my regional Admins / our client]
- Flag a Representative as at risk at: [2] or more missed visits this week
- Compliance goal: [95]%
- Territories to cover: [all I can see / e.g. Northeast, Southeast]
- Key accounts or stores to call out: [e.g. Kroger, Walmart, or "none"]
- Format: [5 bullets and a table / a short email I can forward]
## Steps
1. Get visit compliance for this week and last week from Repsly, grouped by Representative, using my at-risk threshold.
2. Get this week's missed visits: Representative, store, date and the tasks that weren't done. If I listed territories, run it per territory.
3. Get the visits still scheduled for the rest of this week.
4. If I listed key accounts or stores, check them separately and call them out.
## Output
1. **Headline:** compliance this week vs last week vs my goal, with done, missed and upcoming counts.
2. **At risk:** Representatives at or above my threshold, with their missed count and stores.
3. **Missed visits:** a table (Representative, store, date, tasks not done). Show up to 15 rows, then summarize the rest.
4. **Still to do this week:** how many visits are left, and which at-risk Representatives have a heavy schedule.
5. **Follow-ups:** up to 3 suggested actions, based only on the data.
6. **Footer:** date range used, "data as of [today's date]", and whether any list was partial.
## Repsly data rules (keep these)
- Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data.
- Repsly doesn't record why a visit was missed. Never give a reason unless I provide one.
- Always state the date range you used. Weeks run [Monday to Sunday].
- List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool.
- When a name matches more than one Representative, store or form, ask me which one.
- Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone.
- If a tool says the data isn't available for my access level, say so and carry on with the rest.
- Targets, quotas and goals come from me, not Repsly. Label them as mine.
Store visit check
Try: "Check [store name or code]." / "When was [store] last visited?"
--- name: repsly-store-visit-check description: Check what's happening at one store or place in Repsly - recent visits and who made them, time in store, missed visits, forms submitted and what was reported on them, and the next scheduled visit. Use when I ask about a specific store, prep for a client or retailer call, or ask when a place was last visited in Repsly. --- # Repsly store visit check ## Your setup (edit this) - Period to review: [last 30 days] - Flag the store if it hasn't been visited in: [14] days - Forms every visit should have: [e.g. Shelf Audit, or "none"] - Forms whose answers to summarize: [e.g. Shelf Audit, or "none"] - Who reads this: [me / a client or brand partner / a retailer contact] - Leave out: [e.g. Representatives' names if this goes to a client] ## Steps 1. Find the store I name (by name or code). If several match, ask me which one. If nothing matches, also search inactive places. 2. Get completed visits at this store for the period: Representative, check-in and check-out, time in store and tasks done. 3. Get missed visits at this store for the period. 4. Get form submissions at this store for the period, counted per form. 5. For the forms whose answers I want summarized, get the form answers for the period (one form at a time, up to 31 days per request) and keep only this store's submissions. 6. Get scheduled visits at this store for the next 14 days. ## Output 1. **Status:** last visit date, by whom, and whether the store is overdue against my threshold. 2. **Visit history:** a table (date, Representative, time in store, tasks done), newest first. 3. **Missed:** missed visits with the tasks that weren't done. 4. **Forms:** submissions per form, any visit without the expected forms, and a short summary of this store's answers for the forms I listed. 5. **Next visit:** date, Representative and assigned tasks. 6. **Footer:** date range used, "data as of [today's date]", and whether any list was partial. ## Repsly data rules (keep these) - Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data. - Repsly doesn't record why a visit was missed. Never give a reason unless I provide one. - Always state the date range you used. Weeks run [Monday to Sunday]. - List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool. - When a name matches more than one Representative, store or form, ask me which one. - Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone. - If a tool says the data isn't available for my access level, say so and carry on with the rest. - Targets, quotas and goals come from me, not Repsly. Label them as mine.
Form submission tracker
Try: "How are my tracked forms doing this week?"
--- name: repsly-form-submission-tracker description: Track form submissions in Repsly - submissions per form compared with completed visits, who submitted which forms where, and gaps against what I expect. Use when I ask about form completion, form counts, which forms came in, or who didn't submit a form in Repsly. For what was answered on a form, use the Repsly form answers summary skill. --- # Repsly form submission tracker ## Your setup (edit this) - Forms to track: [e.g. Cooler Audit, Shelf Audit, Competitor Activity] - Expected per completed visit: [1 per visit / only at some stores / no fixed expectation] - Period: [last week] - Break down by: [Representative / store / both] - Flag a form when it was submitted on fewer than: [90]% of completed visits ## Steps 1. Find each form I listed. If a name matches several forms, ask me which one. 2. Get submission counts per form for the period, and how many visits each form was submitted on. 3. Get the total number of completed visits for the period (the total is accurate even when the list itself is partial). 4. Compare visits with each form against completed visits, check my expectation and flag the forms below my threshold. 5. For flagged forms, list submissions by Representative or store. If the list is partial, narrow it to one Representative or a shorter period rather than drawing conclusions from part of the data. ## Output 1. **Summary table:** form, submissions, visits with the form, completed visits, % of visits with the form, flag. 2. **Gaps:** Representatives or stores below expectation, with numbers. 3. **Follow-ups:** up to 3 suggested actions. 4. **Footer:** date range used and whether any list was partial. Note: this skill checks whether forms were submitted, not what was answered. Don't comment on answers unless I ask, then use the form answers. ## Repsly data rules (keep these) - Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data. - Repsly doesn't record why a visit was missed. Never give a reason unless I provide one. - Always state the date range you used. Weeks run [Monday to Sunday]. - List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool. - When a name matches more than one Representative, store or form, ask me which one. - Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone. - If a tool says the data isn't available for my access level, say so and carry on with the rest. - Targets, quotas and goals come from me, not Repsly. Label them as mine.
Form answers summary
Try: "Summarize last week's [form name] answers." / "Which categories were skipped most this month?"
--- name: repsly-form-answers-summary description: Summarize what Representatives answered on a Repsly form - answer counts per question, multi-select roll-ups, free-text themes, and the stores or Representatives that stand out. Use when I ask what was reported on a form, what Representatives answered, or for a roll-up of form answers in Repsly. --- # Repsly form answers summary ## Your setup (edit this) - Form to summarize: [e.g. Cooler Audit] - Questions to focus on: [e.g. "Which categories did you not service or complete fully?", or "all"] - Period: [last week / last month] - Break down by: [Representative / store / both] - Flag when: [e.g. an answer is "No", the same category is skipped [3] or more times, or "nothing specific"] - Who reads this: [me / my regional Admins / our client] ## Steps 1. Find the form I named. If several match, ask me which one. 2. Get the form answers for that form and period. Each request covers up to 31 days, so for longer periods get one month at a time and combine them. 3. For each question I listed, count each answer, broken down the way I asked. For multi-select questions, count each option separately. For matrix questions, keep the answers per product. For free-text questions, summarize the common themes and quote up to 3 short examples. 4. Apply my flags and list what matches. ## Output 1. **Headline:** form, period, number of submissions, and the 2-3 things that stand out. 2. **Per question:** a table of answer counts, broken down by Representative or store. 3. **Flags:** Representatives or stores that match my flags, with numbers. 4. **Follow-ups:** up to 3 suggested actions, based only on the answers. 5. **Footer:** date range used, form name, "data as of [today's date]", and anything you couldn't read. Note: photos come as links. Don't describe what a photo shows. ## Repsly data rules (keep these) - Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data. - Repsly doesn't record why a visit was missed. Never give a reason unless I provide one. - Always state the date range you used. Weeks run [Monday to Sunday]. - List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool. - When a name matches more than one Representative, store or form, ask me which one. - Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone. - If a tool says the data isn't available for my access level, say so and carry on with the rest. - Targets, quotas and goals come from me, not Repsly. Label them as mine.
Visit pacing vs target
Try: "Who's behind on visits this week?"
--- name: repsly-visit-pacing-vs-target description: Compare each Representative's visits in Repsly against targets I give you - done so far, still scheduled, missed and whether they're on track. Use when I ask about pacing, targets, quotas, KPIs or who's behind this week or month in Repsly. --- # Repsly visit pacing vs target ## Your setup (edit this) - Target: [25] completed visits per Representative per [week / month] - Different targets for some Representatives: [e.g. "Jamie Torres: 15, part-time" or "none"] - Period: [this week, Monday to Sunday / this month] - Count unplanned visits toward the target: [yes / no] - On track means: done + still scheduled reaches the target - At risk means: done so far is more than [10] percentage points behind the share of the period that has passed ## Steps 1. Get visit compliance grouped by Representative: done, missed and still scheduled. For a week, use the current week. For a month, get compliance from the 1st up to today, then get each Representative's scheduled visits for the rest of the month. Compliance counts planned visits only. 2. If unplanned visits count toward the target, get completed visits per Representative for the period and count the unplanned ones. Only do this if the list isn't partial. Otherwise say the unplanned count isn't included. 3. Compare each Representative with their target and mark them On track, At risk or Off track (can't reach the target even if every scheduled visit is done). 4. For At risk and Off track Representatives, get their missed visits for the period. ## Output 1. **Table:** Representative, target, done, still scheduled, missed, projected (done + scheduled), status. Sort Off track first. 2. **Behind:** for each At risk or Off track Representative, their missed visits (store, date). 3. **Footer:** date range used, which visits were counted, that targets came from me, and whether any list was partial. ## Repsly data rules (keep these) - Use only data from the Repsly tools. If no Repsly tool answers part of the request, say so plainly. Don't estimate or fill gaps from other data. - Repsly doesn't record why a visit was missed. Never give a reason unless I provide one. - Always state the date range you used. Weeks run [Monday to Sunday]. - List tools return a limited number of rows, newest first, plus the true total. If the total is higher than the rows returned, say "showing X of Y" and don't calculate totals, averages or rankings from the partial list. Narrow the request instead (shorter dates, one Representative, store or territory) or use a count or summary tool. - When a name matches more than one Representative, store or form, ask me which one. - Scheduled visit times are local to the store. Visits with no set time say "any time". Completed visit and form submission times come back in UTC: say so, and only convert them when you know the store's time zone. - If a tool says the data isn't available for my access level, say so and carry on with the rest. - Targets, quotas and goals come from me, not Repsly. Label them as mine.
Feedback
Built a prompt or skill that works well for your team, or found one that doesn't? Send it to nika.besker@repsly.com or your Customer Success Manager.