echonext-setup
/echonext-setup
Install, scope, and restore the EchoNext framework and its agent skills in a project. Use when setting up EchoNext in a new or existing repository, moving globally-installed skills into a project, restoring skills from a skills-lock.json after cloning, or adding the skills that are not yet installed.
- Author
- abdussamadbello ↗
- Repository
- echonext ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Install, scope, and restore the EchoNext framework and its agent skills in a project. Use when setting up EchoNext in a new or existing repository, moving globally-installed skills into a project, restoring skills from a skills-lock.json after cloning, or adding the skills that are not yet installed.
Original author description
Install, scope, and restore the EchoNext framework and its agent skills in a project. Use when setting up EchoNext in a new or existing repository, moving globally-installed skills into a project, restoring skills from a skills-lock.json after cloning, or adding the skills that are not yet installed.
How it works
- What cannot be bootstrapped
- Check the current state first
- Case 1 — scope a global install into a project
- Case 2 — add EchoNext to an existing Go project
- Case 3 — fill in a partial install
- Case 4 — restore after cloning
- Scaffolding a new project
- Verifying
SKILL.md preview
--- name: echonext-setup description: >- Install, scope, and restore the EchoNext framework and its agent skills in a project. Use when setting up EchoNext in a new or existing repository, moving globally-installed skills into a project, restoring skills from a skills-lock.json after cloning, or adding the skills that are not yet installed. license: MIT metadata: version: 0.1.0 --- # EchoNext project setup Prepare a repository so both the framework and its agent skills are present and committed. The framework install and the skill install are separate concerns — a project can have either without the other. ## What cannot be bootstrapped A skill is only available once it is installed, so the very first install on a machine is always a manual step: ```bash npx skills add abdussamadbello/echonext ``` Everything below covers what happens after that: scoping an existing global install into a project, adding EchoNext to a codebase, filling in a partial install, and restoring from a committed lockfile. ## Check the current state first Three things vary independently. Determine all three before changing anything: ```bash command -v echonext # CLI present? grep -q abdussamadbello/echonext go.mod 2>/dev/null # framework a dependency? ls skills-lock.json .claude/skills .agents/skills 2>/dev/null # skills present? ``` `npx skills list` reports which skills are installed and at which scope. ## Case 1 — scope a global install into a project Skills installed globally (`-g`) follow the person, not the repository. A teammate or CI agent cloning the project gets nothing. Installing at project scope writes `skills-lock.json`, which is what makes the set reproducible: ```bash npx skills add abdussamadbello/echonext -s '*' -y ``` Run this from the repository root. It writes `skills-lock.json` plus the installed content under `.agents/skills/` and `.claude/skills/`. Commit the lockfile and ignore the installed content: ```gitignore .agents/ .claude/skills/ ``` Project-scoped skills do not replace the global ones; both resolve. ## Case 2 — add EchoNext to an existing Go project Order matters: the framework is a Go dependency, the CLI is a binary, and the skills are neither. ```bash go get github.com/abdussamadbello/echonext@latest go mod tidy ``` EchoNext v1.5.0 requires **Go 1.26 or newer** and Echo v5; typed handlers take `*echo.Context`. Check `go version` first and report a mismatch rather than attempting the upgrade silently — moving a codebase from Echo v4 to v5 changes every handler signature. Install the CLI and the skills as described in `echonext-cli` and Case 1. An existing Echo application does not need restructuring: EchoNext wraps the Echo instance, and typed routes coexist with standard Echo handlers. ## Case 3 — fill in a partial install Installing a single skill with `-s` leaves the rest absent, and a missing skill fails silently — the work just proceeds without its conventions. Compare what is installed against the eight skills in the repository: ```bash npx skills list npx skills add abdussamadbello/echonext -s '*' -y # adds the missing ones ``` The full set is `echonext-cli`, `echonext-domain`, `echonext-handlers`, `echonext-database`, `echonext-openapi-security`, `echonext-middleware-config`, `echonext-integrations`, and `echonext-testing`. ## Case 4 — restore after cloning A repository containing `skills-lock.json` but no installed content restores the exact recorded set, including each skill's `references/` directory: ```bash npx skills experimental_install ``` Use this rather than a fresh `add` when the lockfile exists — `add` resolves to the latest published skills, while the lockfile pins what the project was developed against. ## Scaffolding a new project `echonext init <name> --with-skills` creates the project and installs its skills in one step, and writes a `.gitignore` that already excludes the installed content while keeping `skills-lock.json` tracked. See `echonext-cli` for the CLI's own installation. ## Verifying ```bash npx skills list # eight echonext-* skills echonext --help # CLI resolves go build ./... # framework dependency resolves ```
Versions
The database has no other skills named echonext-setup.
Database snapshot: 13.11.2026 · package version fdea17947716 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100echonext-testing
Write tests for EchoNext APIs using the pkg/contrib/testing helpers — APIClient for in-process HTTP requests, Suite for setup/teardown, and FixtureManager for seeding test data. Use when writing or fixing tests for echonext handlers, services, or endpoints. - 100echonext-database
Work with EchoNext's database layer: GORM models, the generic Repository[T] pattern from pkg/contrib/database, and Atlas migrations/seeds via the CLI. Use when defining models, querying/persisting data, or creating and applying migrations in an echonext project. - 100vibe-skills-manager
Use when installed skills are messy across IDEs, the user is unsure which skills exist globally vs project-level, needs to sync, clean, or recommend installed skills, is setting up a new worktree, or mentions "/vibe-skills-manager". Do not use for authoring or reviewing `skills/vibe-*` content. - 100skills-cli
Use when users ask to discover, install, list, check, update, remove, back up, restore, sync, or initialize Agent Skills, mention `bunx skills`, `npx skills`, `skills.sh`, or `skills-lock.json`, ask "find a skill for X", or want help extending agent capabilities with installable skills. - 98setup-agent-skills
Set up shared skills on this computer. Use when installing this repository's skills, linking them into Claude Code or Codex, or troubleshooting those links. - 100skills-atlas
Find, compare, read, install, update and uninstall public Agent Skills (SKILL.md) from a catalog of about 75,000, with the skills-atlas CLI. Use when the user wants a skill for some task ("is there a skill for…", "find me a skill to…"), asks what skills are installed or…