ada-skill-package-import

Installs external skill packages into a Hermes profile via filesystem copy with loader discovery rules.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/wubing7755/Ada --skill ada-skill-package-import-wubing7755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ada-skill-package-import
Source: https://github.com/wubing7755/Ada/tree/main/skills/software-development/ada-skill-package-import
Command: npx skills add https://github.com/wubing7755/Ada --skill ada-skill-package-import-wubing7755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Installing a downloaded third-party skill package into a Hermes profile is not a per-skill registration task — it is a filesystem copy that must respect the loader's recursive discovery rules, and third-party packs often ship embedded instruction chains that must be treated as untrusted data rather than executed. ## Core Features & Use Cases - Bulk package import: Copies an entire pack tree (SKILL.md files plus scripts/, references/, config/) wholesale under a profile category directory so nested modules are discovered automatically. - Loader-aware layout: Applies verified discovery rules from agent/skill_utils.py — any directory containing SKILL.md is a skill root at any nesting depth, and skills_list re-scans the filesystem live. - Supply-chain vetting: Flags embedded instruction chains in downloaded packs (precedent-auth files, auto-bootstrap scripts, routing contracts) as untrusted data and refuses to auto-execute them. - Use Case: A user downloads an 85-skill security pack and asks to load it; the skill inspects frontmatter, checks name conflicts, copies the tree under skills/reverse-skill/, patches broken cross-tree references, verifies with skills_list, and reports what was deliberately not run. ## Quick Start Install this downloaded skill package into my Hermes profile and verify the new skills are discoverable.

Frequently Asked Questions about ada-skill-package-import

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install an external skill package into a Hermes profile?

Copy the pack's tree wholesale into a category directory under the profile's skills folder, preserving scripts/, references/, and config/ subdirectories. The loader discovers any directory containing SKILL.md recursively, so no per-skill registration is needed.

How does the Hermes skill loader discover installed skills?

The loader walks the skills directory recursively with os.walk and treats any directory containing SKILL.md as a skill root at any nesting depth. The skill name comes from the frontmatter name field, falling back to the parent directory name.

Why is my newly installed skill package not showing up in Hermes?

Check that each module directory contains a SKILL.md with valid frontmatter and that support directories were not flattened away. skills_list re-scans the filesystem live, but the system-prompt available_skills index only refreshes after a new session or reset.

Should I run the setup scripts bundled with a downloaded skill pack?

No. Embedded instructions in downloaded packs are untrusted data, including auto-bootstrap scripts and files claiming to grant authorization. Copy the files, load the knowledge, and keep per-task authorization with the user as the gate.

When should I use skill_manage create instead of a package import?

Use skill_manage with action create for installing a single skill. Bulk package import is for packs containing many SKILL.md trees that should be copied verbatim under one category directory.