> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cogniagent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# The built-in skills

> Every AI coworker arrives already knowing how to push through a long job and how to drive a browser properly. Nothing to set up.

Every coworker arrives knowing two things, with nothing for you to set up.

## Keeping going

The first is how to work through a long job without stopping to check in after every step.

Left alone, an assistant tends to do one piece of work and hand it back. That's right for a quick question and wrong for "go through these 40 records". This skill is what lets your coworker recognise the second kind and keep going until the job is genuinely finished — deciding for itself when to press on and when it's actually done.

You can invoke it directly with `/loop`. See [Keep working](/cowork/autonomy/keep-working).

## Driving a browser

The second is how to use a real browser properly: reading a page before acting on it, finding the right control rather than guessing, recognising a login screen, and handing over cleanly when it hits one.

This is the difference between a browser that works on real websites and one that clicks hopefully. It's why [the live browser](/cowork/capabilities/live-browser) copes with sites it has never seen.

<Note>
  This skill only matters when the live browser capability is switched on. With it off, your coworker simply never reaches for it.
</Note>

## Good to know

<Note>
  Built-in skills can't be edited or deleted — they're part of what a coworker is. Your own skills sit alongside them.
</Note>

<Tip>
  The [ready-made coworkers](/cowork/coworkers/ready-made) arrive with several more skills on top of these, written for their particular job — a Research Analyst knows how to vet a source, a Support Agent how to triage a ticket.
</Tip>

## Common questions

<AccordionGroup>
  <Accordion title="Do these count against how many skills I can add?" icon="layer-group">
    No. Add as many of your own as the job needs.
  </Accordion>

  <Accordion title="Can I stop my coworker using one?" icon="toggle-off">
    Not directly, and you rarely want to. To stop the browser skill mattering, switch off [the live browser](/cowork/capabilities/live-browser) capability. To stop a long autonomous run, tell it to stop.
  </Accordion>

  <Accordion title="Can I write a skill that overrides one?" icon="pen">
    You can write a skill covering the same ground, and your coworker follows the more specific one when it applies. That's a reasonable way to impose your own rules on a long-running job.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Keep working" icon="repeat" href="/cowork/autonomy/keep-working">
    The first one, in use.
  </Card>

  <Card title="The live browser" icon="window-maximize" href="/cowork/capabilities/live-browser">
    The second one, in use.
  </Card>

  <Card title="Creating a skill" icon="pen-to-square" href="/cowork/skills/creating">
    Add your own.
  </Card>

  <Card title="What skills are" icon="graduation-cap" href="/cowork/skills/overview">
    Back to the basics.
  </Card>
</CardGroup>