Edit and import skills
Bring an existing method into Hyperagent from a file or documentation, and keep it current.
When you want to import a method that already lives in a file or documentation, open Skills and select Create skill. From there, you can upload the file, link the source documentation, or have an agent build the skill with you.
Create or import from Skills
The Create skill dialog offers three paths. Choose based on where the method lives today.
Upload a file
Upload a JSON skill export or a Markdown SKILL.md file from your computer (up to 5MB). This is the path for a skill you have already written down or exported from somewhere else.
Link to existing documentation
Point Hyperagent at a documentation URL, or paste the documentation text. It reads the docs and learns the method. This is the path when the process lives in another service's documentation or an API reference you want your agents to follow.
Build from scratch
Have an agent research the topic, or build the skill interactively in chat. This is the path when the method does not exist anywhere yet.
Import never overwrites existing skills
Importing always creates a new skill. If the name is already taken, Hyperagent adds an imported suffix instead of replacing the skill your agents already use. To update an existing method, edit that skill directly rather than importing a fresh copy.
Update a skill
Methods change. A threshold moves, a checklist tightens, or an API adds a field. Edit the existing skill so every agent that uses it receives the improved method on later turns and new runs.
Open the skill
Open it from Skills or from an agent that uses it, then select Edit Skill.
Update the method
Revise the name, description, when-to-use guidance, or documentation. Keep the retrieval guidance and operating method aligned so the agent can still find the skill for the right requests and execute it correctly.
Update scripts when needed
Optional. If the skill runs code, expand the affected script and update its filename, description, or source. Keep its inputs and outputs aligned with the documentation.
Update credentials when needed
Optional. If the service, secret name, or script access requirements changed, update the credential fields and their setup instructions. Secret values remain separate from the skill's documentation and code.
See Skills with APIs and credentials for host locking, script access, and team sharing.
Save and test on a new turn
Save the skill, then start a new turn with an agent that uses it. Test a request that should match the skill and confirm the updated method runs as expected.
Edits affect every agent using the skill
Review a saved change with the same care you would give a shared template or production script. Later turns and new runs use the updated method.
FAQs
Create from a thread when a method emerges from the work. Open Skills to import a file or link documentation, then edit the skill in place as the method changes.