Article
12 Nov 2026
How to get more out of Claude with prompts, skills and connectors
A practical guide to better Claude results: a prompt that interviews you first, skills that handle repeat jobs, and connectors that let Claude work in your tools.

The fastest gains in Claude come from a better opening prompt, a handful of skills that take care of your repeat jobs, and connectors that let Claude work directly inside the other tools your business runs on. Each one saves time on its own. Used together, they change what a single chat can do, and none of them needs any technical background to set up.
Start with a prompt that interviews you
Use the interview prompt for any substantial job. Most disappointing AI output comes from missing context, and the simplest fix is to let Claude ask for it. Copy this and fill in the brackets:
I am trying to achieve [your goal]. I want you to act as my expert [relevant role] and help me achieve it. Before we solve it, I need you to understand the problem. Ask me [number] questions, all at once, to gather as much context as you can. After I've replied with the answers, [the action you want].
Fill in the blanks with care. The goal tells Claude what success looks like, and the role gives its questions an expert point of view. Scale the number to the job, around five questions for a letter and ten or more for something like a strategy paper, and ask for them together so you can answer in one go.
See it in action. My test case was a reference for someone who used to work with us. I cast Claude as an HR director and asked for five questions, and it covered the essentials: the person and their role, the recipient, their best qualities, the tone I wanted and the real reasons behind their departure. Five minutes of answers produced a stronger first draft than I'd normally manage in half an hour.
Edit by hand when one line is off. Claude slipped in "the numbers matter, but the story behind them matters more", a classic piece of AI filler. I swapped it for a line of my own, which took ten seconds. When the rest of a draft is good, fixing one line yourself is quicker than prompting for a rewrite.
Match the model to the job. A letter doesn't need Claude's most powerful model. Sonnet on medium effort handled it easily, which keeps things quick and saves the bigger models for heavier work.
Turn your repeat jobs into skills
Know what a skill does. Think of a skill as a written procedure for Claude, usually one plain-language file explaining how you want a specific job done, so the result comes out consistent each time. Claude keeps a one-line summary of each skill in view and opens the full procedure whenever a request fits.
Switch skills on. Skills rely on Claude's code execution feature. On an individual plan, turn it on under Settings, then Capabilities. On Team and Enterprise plans, an owner switches it on for the business.
Find the skills you already have. Go to Customize, then Skills. The "Your skills" tab shows yours and any your team has shared with you, and Discover lists skills built by Anthropic and partner companies, so you can borrow before you build.
Call a skill directly. Type / in the chat box to pull up your skills, or simply name the one you want. Once I'd finished my letter, one line asking Claude to use our document skill turned it into a branded Word file, with our header, imagery and house formatting in place and the bits I still had to complete marked up for me. Without the skill, that's five to ten minutes of copying, pasting and reformatting for every document.
Build your first skill by interview. The skill that drafts emails in my voice began as a conversation. Claude quizzed me on my writing habits, studied twelve months of my sent mail and wrote the guide from both. The same approach works for any recurring job: get Claude to question you about it, supply some strong examples and have it draft the skill, then review it before you save it.
Read any skill before you install it. Anthropic doesn't review skills that people share, so check what a skill from outside your business does before you switch it on.
Share skills across the team. Owners on Team and Enterprise plans can roll skills out to everyone, share them with named colleagues or publish them company-wide, so every document leaves the business looking like it came from the same place.
Start small. The best first candidates are small jobs you do often, such as writing in your voice, a document template or slide formatting. Bigger skills can come later, like the one I use to audit Microsoft 365 tenants against a long checklist.
Connect Claude to your other tools
Add connectors from the directory. Go to Customize, then Connectors, and browse the directory for the tools you use, such as Microsoft 365, Monday.com and Miro. Click Connect and sign in to each one. You can often add a service that's missing from the directory as a custom connector, which is how I connected Higgsfield for image and video generation.
Refer to your tools naturally. Everyday phrases like "my inbox" or "our deals board" are enough for Claude to pick the right connector.
Combine several connectors in one request. My test gave Claude the role of an account management director and four jobs in one prompt: map my active accounts from a month of Microsoft 365 email, compare them with the Monday.com deals board and flag stale entries, draw a branded opportunity diagram on a new Miro board titled Live Opportunities, and produce a monthly infographic through Higgsfield.
Use Cowork and a bigger model for big jobs. For a request spanning four systems, I moved to Cowork and chose Opus, the top model, which hands pieces of the work to sub-agents so each gets proper attention. It takes a while, so start it and get on with something else.
Answer the questions it asks first. Before starting, Claude asked where the mind map should live, what to do with out-of-date deals, what counts as an account and what the infographic should show about deal values. The account question is a good one to settle with your own team anyway.
Check the output and fix it with a sentence. The Miro board came back clear and useful, with a couple of connecting lines overflowing into each other. One more sentence to Claude sorts that. The infographic was good enough for an internal slide, and I'd treat it as a first draft for anything a client will see.
Be careful what you share. Once connected, Claude inherits every permission you have in your email and CRM, so review what's shared and choose which tools must ask before acting. My recorded demo ran on scrambled, anonymised figures, and any demo you run for an audience should too.
Where to begin
Pick one of these for this week. The interview prompt costs nothing and works on your very next piece of writing, so it's the easiest place to start. Once it's become a habit, build one small skill for a job you repeat every week, and then connect the tool you spend most time copying information out of. Within a month you'll have a chat window that knows how you work, sounds like you and can see what you see, and you'll wonder how you managed with the old one.
Where to go next
Each of these has its own deeper read: the interview prompt, skills and connectors. AI-101 Training teaches all three to your team in a day, and the free Prompt Pit Stop is a quick place to start.