lesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thinglesson 2 of 4 · skills as a team thingskills as a team thingskills as a team thingskills as a team thing
Checkpoint
One last thing before we move on. pass this to mark the lesson done, or skip and keep moving. hop to the next when you're ready.
Lesson two lock-in. The starter declares three variables for the
three ways a skill becomes a team asset. Write three print(f"...")
lines so the output is exactly:
admin provisioning: an admin pushes a skill org-wide, central control
share with colleagues: send a skill directly to specific coworkers
the directory: publish a skill for coworkers to find and install
Type the three lines and run it.