niomartinez/hyper-agentic-engineering / skills/hae-setup
hae-setup
VerifiedInstall, inspect, upgrade or remove Hyper Agentic Engineering while preserving existing agent instructions, hooks and memories.
Set up HAE
Perform setup for the user; do not hand them a list of shell commands to carry out. In a generated skill or plugin, use the bundled scripts/hae.pyz with Python 3.11+. From the reviewed source repository, follow the root SETUP.md and use run.py. Read the selected runtime’s --help; never assume a sibling repository checkout exists. It contains the same deterministic installer as the CLI. If Python is unavailable, report the prerequisite instead of claiming setup succeeded. Use python3 on macOS/Linux and an available Python 3.11+ executable or py -3 on Windows. The CLI prints commands for the current platform; PowerShell paths use its call operator and literal quoting. Never change execution policy or bypass native hook trust.
Keep engineering as the default; its generalized practices and task-routing skill are included. Core behavior remains the default. Published alpha.3 supports core setup without a --profile flag; both profile flags belong to this new runtime. The new optional --profile full-team requires a reviewed current checkout containing it; do not use the alpha.3 runtime or claim the new profile has a tagged release. Read docs/team-setup.md from that checkout before full-team setup. Offer general-work mode when requested; it uses project folders and briefs without coding requirements. Core preserves current styles; the lean preset, capture hooks, Jev and backups are opt-in. Full-team requires engineering and HAE memory, rejects general mode and --no-memory, uses a separately pinned manifest matching 123 upstream entries, materializes 119 eligible skill bundles by default plus portable adapters, and enables Caveman/Ponytail full with session off/on switches. Preserve surrounding instructions. Graphify is model-invocable for graphify-first exploration and Context7 for library documentation; the full community Karpathy method remains explicit-request only. Hooks, Jev, backups and model changes stay off. The optional graphify, ctx7 and ICM installation steps are in the reviewed checkout's SETUP.md; they sit outside plan/apply, need the user's authorization and never write MCP configuration through HAE.
Resolve the intended project folder, verified scope, memory folder and target agents from the request and existing setup. Run plan with those selections. Inspect its conflicts and exact changes; clarify unresolved ownership or competing memory authority. Show the concrete plan before applying, unless the user has already authorized these changes. Never rewrite host configuration yourself or silently replace native memory.
Run apply <plan-id>, then doctor. A configured hook is not proof it ran: Codex trust is reviewed through the native /hooks interface. Do not bypass it. Cowork requires a separately tested plugin/folder environment; a successful CLI run does not establish Cowork support.
Verify one approved save and recall in the selected project. For recovery, use rollback; for removal use uninstall. Both preserve notes and refuse edited owned fragments. Report actual results, unresolved prerequisites and the receipt. Core does not install upstream skills merely because the catalog lists them. A full-team request authorizes its reviewed snapshot; inspect its manifest and exact planned destinations, including any --team-source-dir PATH override. Exclude Anthropic docx, pdf, pptx and xlsx from copying because their license restricts outside-service retention/reproduction; retain all 123 catalog references and route document tasks to native tools unless separate rights are established. Default pinned downloads occur in private plan preparation, with destination writes deferred until apply. Keep the materialized library cold and expose curated host entries. Retain source licenses/notices. Check dependencies and plugin availability per task; never execute upstream installation instructions during setup. Exclude custom release/account workflows, private vault content and account-linked plugins. Team continuity uses sanitized repository handoffs, not private-vault synchronization.
For full-team, finish the native Obsidian setup: use obsidian status, verify the app, register the selected vault when needed, use obsidian open to dispatch the native vault manager, open the selected folder in its interface, and check the intended Home and memory guide in the app. App installation is a separate authorized native action through the official channel; never silently download it. The optional Obsidian CLI is checked when needed and does not block HAE save/recall. Report missing app, registration, restart or CLI actions precisely; vault files alone do not prove completion.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 468k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |