# Choose, download, and import

Check responsibilities, sources, and configuration before host preview and confirmation.

## Start with the output you need

1. Search for a goal such as meeting preparation, bug retesting, or a weekly report.
2. Open details and compare responsibility, inputs, outputs, skills, sources, and permission needs.
3. Start with one role and define a handoff before adding another.
4. Check body language and platform assumptions, especially in English source adaptations.

Choose bot-role for an ongoing responsibility and method; choose task-workflow for a step template organized around an output, reusable as needed. Preview and confirm either in the host, then check tools, accounts, and human handoffs. A workflow template does not itself provide automatic orchestration or a verified runtime state; assess the actual output against acceptance criteria.

## Choose the download type

| Situation | Recommendation |
| --- | --- |
| First use | One role or a small scenario download |
| Need English content | Choose its configuration in English mode |
| Large collection | Use release parts with at most 200 Bots per Fleet file |
| Only need Agent context | Use Copy for Agent or one role context file |

Shared Bots are source links, not installable configurations from this site. Identical names do not prove identity; compare author, platform, and URL.

## Preview and confirm in the host

1. Keep the file with its role ID, version, language, and digest.
2. Use the host's current configuration import entry, select the Fleet file, and read the preview and confirmation.
3. Check new names, collision handling, and existing primary Bot state.
4. After confirmation, separately configure models, tools, and accounts, then start an explicit task.

The repository README documents a Settings → Data & Sync → Import configuration example. Follow the entry in your current host version. Downloading and importing do not themselves start tasks or environments.

## Check after import

- Compare responsibility by ID rather than name alone.
- Record actual host-returned Bot IDs for later upgrade reconciliation.
- Accept a fictional short task before supplying real materials.

- [Configuration market](https://harzva.github.io/awesome-bot/?lang=en)
- [Troubleshooting](https://harzva.github.io/awesome-bot/handbook-troubleshooting.en.html)

Append one record per import to a local or access-restricted team log, preserving history; link upgrades to the earlier record ID. Separate source identity from actual host identity, and never treat a source ID as the new Bot ID. If the host does not show an ID, write “not obtained” and append evidence when available; a missing ID is not evidence of the same identity. Passing a fictional task establishes usability for that task; upgrade identity still requires evidence such as the actual Bot ID in the same host.

```text
Record ID:
Earlier record ID (for upgrades):
Source URL:
Source ID:
Source version / language:
Downloaded filename:
File SHA-256 (mark if unchecked):
Host / version:
Import time:
Actual host name:
Actual host Bot ID (write “not obtained” if hidden):
Fictional task and result:
Task usability: yes / no / unverified
Upgrade identity reconciliation: complete (attach evidence) / evidence pending
```

## Sources

Sources checked: 2026-10-25

- [Import examples](https://github.com/Harzva/awesome-bot/blob/main/README.md)
- [Import and identity reconciliation](https://github.com/Harzva/awesome-bot/blob/main/INTEGRATION.md)
- [Release parts and checksums](https://github.com/Harzva/awesome-bot/blob/main/docs/publishing.md)