Reusable skills and reviewed materials
A skill describes how to do a kind of work; it does not add an account, tool permission or paid provider. Choose a relevant enabled skill from the agent’s available catalog. Its declared tools and runtime dependencies must actually be available.
Inspect and update a package
Open the skill’s details to inspect its instructions, source declaration, version, file inventory, checksums and license information. Load only the needed reference or asset. Reading a script does not execute it, and a declared origin or checksum does not independently prove authorship or redistribution rights.
Imported packages start disabled. Review the instructions and required resources before enabling the skill for its intended audience. For an update, compare added, changed and removed files and license changes. A stale preview must be refreshed before replacement. Editing only the main instructions does not silently certify the old package resources as a matching version.
Prepare a useful deliverable
For code, ask for a specification, a bounded implementation plan and review against the original acceptance conditions. Reuse the existing component catalog and project conventions. A package name, compiling example or screenshot is not proof that keyboard, focus, menus and editing work in the real interface.
For a business document or brand material, supply the actual source, target audience, language, output format and approved visual identity. Distinguish facts from proposed wording. Inspect real pages or slides for complete text, readable type, tables and image placement; verify the exported file rather than accepting only a preview description.
For diagrams, MCP integrations and operational instructions, require current source references and clear unsupported boundaries. A skill may explain a connector but cannot authorize its connection or an external write. Existing current-user access, approvals and data-processing rules remain in force.
Image or video generation requires an available configured provider when the chosen workflow uses one. Review any paid action before starting it. A reusable template must not silently create new paid work. For an instructional video, follow the separate source and rendered-clip review before accepting the final file. Separate future design or voice studio products are not activated by loading a skill.