Sourcing Agent
Recruiters: Build and refresh a candidate research Sheet.
View Sourcing Agent →Start with a creative brief, research synthesis or draft calendar. See fictional examples and free workflow files, with access and action limits made explicit.
Start with one-off drafting from supplied notes. These examples describe intended outputs, not tested integrations or guaranteed scheduled work.
| Task | Inputs | Reviewable output |
|---|---|---|
| Creative brief | Approved goal, audience, offer and source notes | Brief with unknown fields and review questions |
| Research synthesis | Supplied research notes with source URLs | Themes, disagreements and evidence gaps |
| Content calendar | Approved channels, assets, timezone and reviewer | Draft queue, never automatically published |
Juniper Studio supplies a launch goal and audience but no approved price. Ask: "Using only these fictional notes, draft the Goal, Audience, Offer, Proof, Channels and CTA fields. Mark missing fields unknown and list reviewer questions. Do not publish or schedule." Expected: offer and proof stay unknown; the output asks for evidence rather than invent a discount or customer result.
Download free three-file pack Preview the campaign brief pack · Muse calendar setup guide
Reading files does not connect an account, save a document or activate a recurring job. Confirm what the particular Muse product supports; use the draft-only fallback when tools are unavailable.
Verified free workflows come first. Each card links to a live existing product. Free copy-ready prompts follow below.
Recruiters: Build and refresh a candidate research Sheet.
View Sourcing Agent →Marketing: Maintain a recurring content calendar Sheet.
View Social Media Calendar Agent →Sales: Keep follow-ups and next steps current in a Sheet.
View Follow-Up & Pipeline Agent →Finance: Produce a recurring management report artifact.
View Management Reporting Agent →Bookkeepers: Run the reconciliation checklist and exception Sheet.
View Reconciliation Agent →Real estate: Maintain a closing checklist and review queue.
View Transaction Checklist Agent →Founders: Publish a recurring KPI update from a stable Sheet.
View KPI Update Agent →Use these prompts at no charge. They are not products. Only genuine matches inside this section carry a clearly marked free agent download link.
Trigger: an approved sales or fundraising brief is complete. Inputs: audience, problem, proof, metrics, ask and brand assets. Work: build a conclusion-led story and source every claim. Output: Google Slides deck plus evidence log. Boundary: no invented traction or external share. Result: a review-ready deck with one decision per slide.
Use Muse to make the writing clear and natural. Turn my brief, facts and brand files into a clear pitch deck. Keep one main idea on each slide and do not invent numbers. Add source notes for important claims. Show me the finished presentation before sharing it.
Trigger: a reporting period closes. Inputs: approved metrics, prior report and narrative rules. Work: explain changes and build charts and conclusion-led slides. Output: presentation plus source table. Boundary: publication and distribution require approval. Result: every figure matches the source period and workbook.
Use Muse to make the writing clear and natural. Turn my approved numbers and notes into a clear presentation. Explain what changed, use simple charts and add a source table. Do not invent missing data. Show me the finished presentation before sharing it.
Trigger: a discovery-call transcript is approved. Inputs: transcript, service scope, proof, pricing rules and proposal template. Work: extract needs, objections and commitments, then draft a tailored proposal. Output: proposal Doc or Slides with transcript evidence. Boundary: no unsupported promise, price change or client send. Result: each proposed solution maps to a stated customer need.
Use Muse to make the writing clear and natural. Read the approved call transcript and draft a proposal for that customer. Use their needs, questions and agreed next steps, and follow my pricing rules. Mark anything that was not agreed. Show me the final proposal before sending it.
Trigger: the user asks for a meal with location, timing and constraints. Inputs: delivery address, cuisine, dietary needs and budget. Work: compare live menus, fees and delivery times and prepare a cart. Output: final order summary. Boundary: the user confirms items, address and total before purchase. Result: the chosen order matches constraints and no charge occurs before approval.
Use Muse to make the writing clear and natural. Find food that matches my location, diet, budget and delivery time. Compare the final price and arrival time for a few good choices. Show me the restaurant, items, address and total. Ask before placing the order or paying.
Trigger: an approved site brief or issue enters the backlog. Inputs: source repository, design rules, content and deploy route. Work: build or patch the site, run tests and preview changes. Output: versioned source and deployment report. Boundary: production deploy, domain and payment changes need approval. Result: acceptance tests and visual QA pass on the intended pages.
Use Muse to make the writing clear and natural. Use my approved site files and brief to make the requested website change. Test the links, forms and mobile layout, and give me a preview. Keep a copy of the earlier version. Do not publish the change until I approve.
Trigger: a user gives a research question and decision criteria. Inputs: scope, preferred sources, recency and exclusions. Work: search, open primary sources and compare findings. Output: cited research Doc or decision Sheet. Boundary: no login, purchase, form submission or disclosure outside scope. Result: every action-driving claim has a live source and checked date.
Use Muse to make the writing clear and natural. Research my question using current, trusted sources. Open the main sources, compare what they say and include the links and dates. Tell me what is certain and what is unclear. Do not sign up, contact anyone or Download anything without asking me.
Trigger: weekdays at 7:30 AM or when a tracked company, topic or regulator is named in a credible source. Inputs: tracked terms, source preferences, exclusions, recency window and prior-news log. Work: search current sources, open the primary announcement, verify coverage and deduplicate by canonical URL plus event fingerprint. Output: a dated news-monitor Sheet and short briefing Doc. Boundary: no public post, investor note or customer message without approval. Result: only new verified events appear once, with source and checked time.
Use Muse to make the writing clear and natural. Every weekday at 7:30 AM, check trusted news and official sources for my topics. Skip stories I have already seen and include the original links and dates. Give me a short summary of what changed and why it matters. Do not publish or send it anywhere without asking me.
Trigger: the approved weekly publishing clock after the news/source queue closes. Inputs: audience, editorial angle, approved source queue, prior issues, voice and length. Work: select non-duplicate stories, summarize with links, write the intro and sections, then check claims and repeated topics. Output: newsletter Doc plus issue log. Boundary: no subscriber import, email send or publication without exact audience-and-copy approval. Result: a complete issue with every item sourced and no story repeated from the prior issue.
Use Muse to make the writing clear and natural. Once a week, turn my approved links into a short newsletter for my audience. Do not repeat stories from earlier issues. Add a clear title, short sections and links to every source. Show me the full draft before publishing or sending it.
These are informational patterns grounded in the sources below. They are not products sold by AI Agent Skills.
Trigger: an owner supplies a target customer, constraints and research links. Muse turns them into a launch-plan Doc with assumptions, experiments and decision dates. Boundary: no purchase, post or outreach.
Trigger: a campaign objective and approved brand references are provided. Muse develops distinct concepts and writes a presentation-ready brief with message, visual direction and risks. Boundary: no unsupported claim or asset publication.
Trigger: a designer adds interview notes and research questions. Muse groups evidence into user problems and produces a discovery Doc with quotes and open questions. Boundary: it does not claim statistical validity.
One-off: use a clear prompt when the question changes each time. Recurring: use a stable schedule or trigger only when the same sources and checks apply. Artifact rule: finish in a Form, Doc, presentation or Sheet, not a chat-only answer.
Use the Muse setup hub for profession guides and current setup notes. AI Agent Skills is independent and is not affiliated with or endorsed by Muse.
Community evidence also reviewed: Reddit discussion of real-world assistant uses. Community claims were treated as leads; product-specific claims above rely on official or reported sources.
Reviewed 18 September 2026 · AI Agent Skills team.