Give Skills Files (Artifacts)
Open in CMSArtifacts are files your agent owns, such as checklists, summary templates or pictures, grouped into folders. A skill can be given whole folders, and while that skill is open the agent can read the files in them or show the pictures. In this tutorial you create a folder, upload a file, and let a skill use it.
Before you start
- Read Teach Your Agent Skills to understand what a skill is.
- Have the file ready. For text the agent should read, use a plain-text file such as
.mdor.txt. To follow along, download the sample file kg-f12-checklist.md that Atlas, Kirana Group's operations assistant, uses for capex requests. - You know how to test and publish changes. See Preview and Publish Changes.
How artifacts work
- Files live in folders, and access is given by folder. You never give a skill a single file. You tick a folder in the skill, and the skill may read every file in it, including files you add later.
- The agent reads a file only while a skill that may read its folder is open. When the skill closes, its file access goes with it.
- The agent refers to a file as folder/file, for example
capex-request-kit/kg-f12-checklist.md. Use the same path when you mention a file in a skill's instructions. - Each folder is private or public. A private folder is for reference material the agent reads. A public folder is for pictures the agent shows in its answers: anyone who has a file's URL can open it, without signing in.
- Artifacts are not Knowledge. Knowledge documents are searched on every question. An artifact is read only when a skill that uses it is open, so it suits material that only matters for one procedure.
Step 1: Create a folder
- In the agent sidebar, open Skills β Artifacts. The page has one table, Folders and files. Click a folder row to open it in place and see its files under it.
- Click New folder.
- The Add files panel opens on the new-folder form. Fill in:
- Name (required): the folder name the agent writes before the file name. Up to 60 characters, no slash, unique on this agent. Example:
supplier-onboarding-kit. - Description: a note for you about what belongs in the folder. The agent never sees it. Up to 200 characters. Example:
Supplier registration forms, the onboarding checklist and the welcome letter template.
- Name (required): the folder name the agent writes before the file name. Up to 60 characters, no slash, unique on this agent. Example:
- Under Who can open files, choose Private (the default) or Public. Click Create folder. The folder is saved straight away.

Step 2: Upload a file
- Click Upload file. The Add files panel opens.
- Under Upload to, choose the folder, here
capex-request-kit. Choose the file, herekg-f12-checklist.md, or drop several files into the panel. Click Upload 1 file. - Open the folder's row. The file appears under it, with its path as folder/file. A file that replaces one with the same name shows Replaces existing in the panel before you upload.
Changes on this page are saved immediately; there is no Save button.

For Atlas, the file kg-f12-checklist.md holds the fields of form KG-F12, the cost centre for each site, the attachments required by value, and the request summary template the skill must follow:
# Kirana Group: KG-F12 capex request kit
## Fields on form KG-F12 (Procurement Portal)
- Project code (KG-0000) and project name
- Site and cost centre (see the table below)
- Total project value in USD, including tax, contingency and all phases
- Requester and Department Head
- Expected start date and completion date
- Short justification (max. 300 characters)
## Cost centres
| Site | Cost centre | Regional Director |
|---|---|---|
| Jakarta | CC-110 | West region |
| Bekasi | CC-120 | West region |
| Surabaya | CC-210 | East region |
| Makassar | CC-310 | East region |
## Attachments by value
- Up to USD 250,000: one vendor quotation
- Above USD 250,000: at least three vendor quotations
- Above USD 1,000,000: also a business case with payback period, and a risk register
## Request summary template
Use this exact layout when you draft the summary for the requester:
KG-F12 SUMMARY
Project: <code> <name>
Site / cost centre: <site> / <cost centre>
Total value (USD): <value>
Approval chain: <approvers in order, from SOP-FIN-007>
Attachments: <list>
Submit at least 10 business days before the Board Investment Committee if the value is above USD 5,000,000.
File types and limits
| File size | Up to 10 MB per file. A bigger file is skipped and marked Skipped in the panel. |
| Text the agent reads | Plain text, such as .md, .txt or .csv. The agent reads a private file as text, so keep documents like PDFs or Word files in Knowledge instead. |
| Pictures the agent shows | Put them in a public folder. The agent shows a picture by putting its URL in the answer. |
| How much is read at once | The first 16,000 characters of a file. If a file is longer, split it into smaller files so the agent can read the part it needs. |
| Same file name | Uploading a file with the same name into the same folder replaces the old one. The panel says Replaces existing first. |
| Folders | Up to 30 folders per agent. |
Step 3: Let a skill read the folder
- Open Skills β Skills and click the skill's row, or open its row menu and choose Edit skill. For a new skill, click Add skill. The skill editor opens as a side panel on the right.
- Under Folders this skill may read, tick the checkbox in front of the folder, here
capex-request-kit. Each folder shows whether it is public or private. Clicking only the folder name can miss the checkbox, so check that it is ticked. - In Instructions, say when to use the file, with its full path. For example: "Open capex-request-kit/kg-f12-checklist.md. Find the cost centre for the site and the attachments required for the value."
- Click Apply (or Add), then Save all changes at the bottom of the window. The Folders column of the skill list now shows 1.
If there are no folders yet, the panel shows a note pointing you to the Artifacts page. See Create a Skill for all the other fields.
Make a folder public or private
Open the folder's row menu and choose Make public or Make private, then confirm. The folder row shows a Public or Private chip.
- Make public makes every file in the folder readable by anyone who has its URL, without signing in. Use it only for pictures the agent is meant to show, never for internal material such as cost centre lists, checklists or procedures.
- Make private stops the files being reachable by URL. Pictures already shown in past conversations stop loading.
Changing visibility moves the files to different storage, so any file URL that was already shared stops working.
Edit or delete
- Edit a folder: open the folder's row menu and choose Edit folder to change its name or description. Visibility is changed from the row menu, not in this dialog. If you rename a folder, update the file paths in your skills' instructions too.
- Upload to a folder: open the folder's row menu and choose Upload file here.
- Delete a file: open the file's row menu, choose Delete file, and confirm. A skill that mentions it can no longer read it.
- Delete a folder: open the folder's row menu, choose Delete folder, and confirm. Every file in it is deleted too, and the confirmation names the skills that lose access.
Check the result
-
Open Preview and start a new chat.
-
Ask something only the file can answer. For Atlas:
Help me prepare a KG-F12 capex request for KG-2063, the Bekasi rooftop solar project. Total value USD 1.35 million, including tax, contingency and all phases. -
The answer should use facts from the file. Atlas finds cost centre CC-120 for Bekasi and, because the value is above USD 1,000,000, asks for at least three vendor quotations, a business case with payback period, and a risk register. Neither fact is in Atlas's knowledge; both come from
capex-request-kit/kg-f12-checklist.md.
If Atlas says it cannot find the checklist, the skill was probably saved without the folder. Check that the Folders column shows 1 for the skill on the Skills page.
Artifacts are saved to your agent's draft, so Preview uses them right away. Click Publish when you are ready, so the live agent uses the same files. See Preview and Publish Changes.
Next steps
- Next in the journey: Talk by Voice, to let people speak with your agent.
- Create a Skill: write the procedure that uses your files.
- Field-by-field reference: Artifacts.