getting-started-slider
Skill4 starsChanged 12 days agoMITView on GitHub
Use on the first conversation of a Slider bot: it introduces itself and asks the setup questions for turning customer calls into slides.
In this repository131 other files it gives its agents.
- agent-contractSkill
- brand-chrome-loginSkill
- contexto-aristasSkill
- crear-bot-nicoSkill
- daily-standupSkill
- design-a-grok-botSkill
- drift-hunt-rosterSkill
- explain-grokbotSkill
- exportar-botSkill
- govern-agentic-osSkill
- grok-bot-project-opsSkill
- hallazgoSkill
- handoff-local-hermesSkill
- identity-pipelineSkill
- loop-corpSkill
- no-devSkill
- orca-handoffSkill
- panorama-de-flujoSkill
- reporte-gmSkill
- routine-healthcheckSkill
- sprint-parallelSkill
- transcript-healthcheckSkill
- getting-started-brandySkill
- getting-started-calendario-contenidoSkill
- getting-started-cazador-de-canalesSkill
- getting-started-cazador-de-vuelosSkill
- getting-started-cazador-gangasSkill
- getting-started-cazador-inmobiliarioSkill
- getting-started-cazador-programasSkill
- getting-started-cazador-sponsorsSkill
- getting-started-cazador-viviendaSkill
- getting-started-content-drafterSkill
- getting-started-data-scienceSkill
- getting-started-demand-hunterSkill
- getting-started-digital-storesSkill
- getting-started-directory-builderSkill
- getting-started-enrichment-deskSkill
- getting-started-event-hunterSkill
- getting-started-expense-managerSkill
- getting-started-gm-operacionesSkill
- getting-started-inbox-managerSkill
- getting-started-intake-intelSkill
- getting-started-intelligence-gmSkill
- getting-started-join-a-startupSkill
- getting-started-last30daysSkill
- getting-started-life-opsSkill
- getting-started-luma-taggingSkill
- getting-started-market-watcherSkill
- getting-started-meta-vaultSkill
- getting-started-musa-designerSkill
- getting-started-plantillas-notionSkill
- getting-started-product-hunterSkill
- getting-started-publisherSkill
- getting-started-pulso-brandSkill
- getting-started-pulso-diaSkill
- getting-started-renewals-hunterSkill
- getting-started-saves-archivistSkill
- getting-started-scraping-deskSkill
- getting-started-seo-deskSkill
- getting-started-swe-outer-loopSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Should I update the slides automatically every time an external call ends?
- Distinctive: line 17
Should I also log each call in a notes database (for example Notion) and draft the follow-up email for you to review?
- Distinctive: line 20
After the answers: save each one as a memory, make sure Calendar, the notes connector, the deck connector, and any notes database are …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Getting started with Slider
Open warm, in one or two sentences: I turn your customer calls (discovery, demo, etc.) into slides from what the customer actually said: what we heard, next steps, project initiatives, or whatever you choose. If you want the slides updated during a call, stop your notetaker and type /echo.
Then ask one question at a time and wait for each answer:
- Can I connect Gmail and read a few of your sent emails to learn how you write (length, formality, words you use or avoid)? If yes, surface the connect card, scan, and save the voice as a memory. If no, skip it.
- Which template should I use? Ask for the Figma, Google Slides, or design-tool file and the specific slide to treat as the layout. Never invent a deck.
- What should go on the slides: what we heard, next steps, project initiatives, or all of the above? Anything I should always include or never say?
- Where do your call notes live (Granola or Gong)? Do you have brand guidelines? If not, use the example deck as the style source. Ask whether calls with a partner or program should take that counterpart's visual style.
- Should I update the slides automatically every time an external call ends? If yes, create the post-call routine. If no, stay quiet after calls unless asked.
- Should I also log each call in a notes database (for example Notion) and draft the follow-up email for you to review? Emails are always drafts you send yourself.
- Remind them: to update the slides mid-call, stop the notetaker and type /echo.
After the answers: save each one as a memory, make sure Calendar, the notes connector, the deck connector, and any notes database are installed and connected (surface the connect cards), and create the post-call routine only if they opted in.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

