Skip to main content

Skills

A Skill in AgenticHub is a reusable unit—common for resume screening, knowledge search, text processing, and building dedicated agents. You can evolve skills in three ways: skill-creator (natural language to a first testable version), in-repo file editing in the skills repository, or Git clone, local dev, and push. Menus follow production.

Terms and objects​

  • Skill — A module you mount on an agent or flow; usually defines inputs, outputs, and business rules.
  • skill-creator — For users who prefer description over heavy config: natural language drives generation and iteration.
  • Skill repository — Central place to store and distribute skills: create your own or search shared content and get Git URLs.

UI screenshots​

Create a Skill with skill-creator​

Best for quickly validating an idea with minimal file work. Sign-in: Account and environment.

Steps

  1. Open skill-creator from the main or skills navigation.
  2. Describe inputs, outputs, and core logic; if the write-up is too vague, the system will ask follow-ups.
  3. After the first version, find the skill in the skill bar or similar.
  4. Fill invocation URL or sample params, send a test; refine in natural language or move to in-browser file editing for fine control.
  5. When it works, complete name, description, visibility, then use privately or publish.

Notes

  • Be explicit about data shapes and edge cases; avoid hand-wavy words.
  • Before wide publishing or production use, regression-test on multiple examples.

Edit in the skills repository​

Best for users comfortable with JSON, YAML, XML, and full control of layout and API definitions.

Steps

  1. Open Skills → Repository, New (often top right).
  2. Set repo name (English is recommended to match Git habits), license, and other metadata, then open the editor.
  3. Maintain skill definitions and scripts to platform rules; each save has history for diff and rollback.

Prerequisites

  • Think through inputs, outputs, error codes, and timeouts before large edits.
  • Use editor plugins or linters to validate syntax before save.

Clone with Git, develop locally, push​

Best for teams forking public or community skills and using local IDEs and branches.

Prerequisites

  • Git installed (2.20+ recommended), user.name / user.email aligned with the platform identity.
  • In the skill repo, find the public skill and copy HTTPS or SSH from Download skill (or equivalent).

Steps

  1. git clone to a local folder.
  2. Edit core config (often skill_config.json or skill.yaml—use what the repo uses); bump version and changelog.
  3. After local checks, git add, commit, push with meaningful messages for review.

Online vs. Git

  • In-browser edit: small, fast, traceable. Git: multi-person, branches, and local tests. Use one as primary or combine by phase.

Mounting, composition, and operations​

  • When mounting, satisfy the main path first, then add enhancement skills; on conflicts, disable one by one to locate the cause.
  • Document call order and dependencies for multiple skills on one instance.
  • Skills = stable steps; Prompts = context and style; Tools = external facts and actions—clear boundaries speed debugging.
  • Deprecate or replace unmaintained skills to reduce supply-chain risk.

Publish, share, and security​

  • Before public release or writing to a shared repo, run security and redaction review; include usage notes and example I/O.
  • Visibility, review, and takedown follow current product policy; never put secrets in public descriptions or examples.