1.6 Work: Combine Several Skills Into One Work Package
The Skill in 1.5 answers "how does this class of task get done". Real work rarely has only one step.
Take cross-border e-commerce operations: watch competitors, read reviews, improve listings, track ads, write the weekly report. Five tasks, five capabilities, one business chain. Working out "which Skills do I need this time" before every run becomes a burden quickly — and everyone on the team makes a different choice.
Work packages a group of related Skills into one unit.
What a Work Is
| Dimension | Skill | Work |
|---|---|---|
| Contains | A method for one class of task | A group of related Skills |
| Loading | Enters context by default after installation | Uses its included Skills as a whole when selected in a task |
| Answers | "How does this class of task get done" | "Which capabilities does this whole job need" |
| Fits | Scattered day-to-day tasks | One complete business chain |
The second row is the only structural difference from a Skill, and the most common misunderstanding:
After adding a Work in 【Explore】, open 【Add context】 → 【Choose works】 in the task and select it.
Check in this order: confirm the Work is enabled on its detail page, then check its tag in the current task.
How Work and Skill Divide the Job
The relationship is hierarchical: a Skill defines one capability, a Work defines how a group of them are combined.
| Your situation | Use |
|---|---|
| A single task you do occasionally | Skill |
| One job that runs three or more steps | Work |
| Team members pick different Skills and output varies | Work — fix the combination |
| You only want one class of task done to a standard | Skill |
What Work really solves is not fewer clicks but consistency across a team: everyone runs the same combination and gets the same process.
Adding and Using: Two Actions
For adding, enabling, and checking the task tag, see the demo in AOS Work: Work.
- Add. Open 【Explore】 → 【Work】, read the description and 【Includes】, then click 【Add】 and follow the dialog.
- Select it in a task. Click 【New Chat】, open 【Add context】 → 【Choose works】, select the Work, and check its tag before sending.
- Skill: method for one task class
- Skill: method for another
- Packaged as a Work
- Selected in a task
- You state the goal and acceptance criteria
- The Work loads its Skills as a whole
- The agent executes with the set
- You review the result
Select the Work as a whole in a task. Review 【Includes】 on its detail page, and use 【Enabled】 to control whether the resource is enabled.
A Work does not invoke Skills for you. It prepares the capabilities; what gets done is still decided by your instruction.
An Example
An e-commerce operations Work packages six capabilities: competitor monitoring, review analysis, listing optimization, keyword research, ad performance analysis, and the weekly report.
Once selected, one instruction is enough:
1. Did any competitor change price overnight? What is my price gap?
2. Did any competitor change title or bullets? List the changes.
3. How many new reviews did each of us get? What is the sentiment split?
4. Which issues dominate the negative reviews? Output: write to the "Daily Check" view in Base, one row per product.
The agent calls competitor monitoring and review analysis in turn and writes the results back to the table. When complete, check the records in the specified Base table against the source data.
That is using a Work. Designing your own — how to split the steps and where data hands over — is covered in 2.5.
When to Use a Work
| Test | Choice |
|---|---|
| A single task that may not recur | A Skill, or the requirements in the prompt |
| Three or more steps, each with a settled method | A Work |
| The chain runs every week | A Work, and consider attaching it to a scheduled task (see 2.1) |
That last row is where a Work earns its place: once a chain can be re-run, it stops being manual work and becomes a process you re-run.
Summary
A Skill is one capability; a Work is a combination of capabilities. Select a Work and the whole set is in place.
The next lesson covers Connectors: complete the required authorization after adding one, then check an actual query result.
1.5 Skill: Add Your First Reusable Capability
You repeat the same request every week. A Skill lets you say it once and fixes the method in place.
1.7 Connector: Reach External Systems and Authorize Access
Letting the agent read an inbox or book a meeting requires a channel to the outside system. This lesson covers how that channel is built and which authorization it needs.