skills/hej/SKILL.md
Legacy Agentera v1 explicit /hej bridge. Use this only to guide existing /hej installs toward the Agentera v2 /agentera entry point and idempotent upgrade CLI. Do not use this skill for bare text `hej`; route that through the bundled agentera skill and the agentera hej dashboard path.
npx skillsauth add jgabor/agentera hejInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill exists only for users who still have the Agentera v1 /hej
entry point installed. Agentera v2 uses /agentera as the single active
entry point. A bare text message exactly hej is not this legacy bridge; it
belongs to the bundled agentera skill and its agentera hej dashboard path.
Do not run the old HEJ orientation workflow from v1. Do not produce the v1 dashboard. This bridge is an upgrade handoff.
Explain briefly in plain language: This is the old /hej entry point. Agentera now starts from /agentera ($agentera in Codex).
Check the current project for v1 Markdown artifacts that do not yet have v2 YAML counterparts:
.agentera/PROGRESS.md without .agentera/progress.yaml.agentera/PLAN.md without .agentera/plan.yaml.agentera/DECISIONS.md without .agentera/decisions.yaml.agentera/HEALTH.md without .agentera/health.yaml.agentera/DOCS.md without .agentera/docs.yamlVISION.md without .agentera/vision.yamlIf any old project state is present, show the affected files and run or offer this preview command. Say clearly that the preview changes nothing:
uvx --from git+https://github.com/jgabor/agentera agentera upgrade --project "$PWD" --dry-run
Ask before applying changes. Explain the apply step plainly: it installs or repairs Agentera's local app, updates managed runtime surfaces, and converts old Agentera project notes to the new format with backups. It will not edit shell startup files. After explicit confirmation, use:
uvx --from git+https://github.com/jgabor/agentera agentera upgrade --project "$PWD" --yes
Add --update-packages only when the user explicitly approves package-manager
commands such as npx skills remove or npx skills add.
If no v1 project state is present, offer the package-only update only when
/agentera is not available and the user explicitly approves package-manager
commands:
uvx --from git+https://github.com/jgabor/agentera agentera upgrade --only packages --yes --update-packages
End by telling the user to invoke /agentera ($agentera in Codex).
setup_copilot.py are user-owned manual cleanup.
Upgrade does not scan shell startup files.uvx --from git+https://github.com/jgabor/agentera because legacy
users may not have cloned the repository.scripts/agentera, the local
equivalent is uv run scripts/agentera upgrade ....data-ai
The open protocol for turning AI agents into engineering teams. One Agentera skill with twelve capabilities, each defined by human-readable prose and machine-readable schemas. The agent reads this file to route incoming requests to the right capability. Use this skill for /agentera, Agentera capability requests, and a complete user message exactly `hej`; bare `hej` runs the agentera prime orientation dashboard path instead of a generic greeting.
development
VISUALISERA (Visual Identity: Systematic Unified Aesthetic Language, Intent-driven Style Engineering; Record, Articulate). ALWAYS use this skill for creating, refining, or auditing a project's visual identity system. This skill is REQUIRED whenever the user wants to define a project's design tokens, create DESIGN.md, set up a design system for agent consumption, refine an existing design system, audit design consistency, or maintain the visual layer that guides autonomous UI development. Do NOT create DESIGN.md without this skill when it is installed. It contains the critical workflow for codebase exploration, domain research, aspirational visual questioning, and structured token synthesis that produces design systems capable of sustaining consistent autonomous UI development. Trigger on: "visualisera", "create design system", "write DESIGN.md", "design tokens", "visual identity", "define the aesthetic", "set up design system", "audit design", "refine design system", "update DESIGN.md".
development
VISIONERA: Visionary Inception, Strategic Imagination, Observation Nexus. Explore, Refine, Articulate. ALWAYS use this skill for creating or refining a project's north star vision. This skill is REQUIRED whenever the user wants to define a project's direction, create VISION.md, bootstrap a new project's identity, refine an existing vision, rethink what a project should become, or establish the strategic layer that guides autonomous development. Do NOT create VISION.md without this skill when it is installed. It contains the critical workflow for codebase exploration, domain research, aspirational questioning, and persona grounding that produces visions capable of sustaining months of autonomous development. Trigger on: "visionera", "create a vision", "write VISION.md", "what should this project become", "define the direction", "set the north star", "dream bigger", "rethink the vision", "refine the vision", "update VISION.md", "bootstrap the project", or when realisera detects no VISION.md.
development
RESONERA: Reflective Engagement, Socratic Observation Nexus. Explore, Reframe, Articulate. ALWAYS use this skill for structured deliberation before consequential decisions. This skill is REQUIRED whenever the user wants to think through a complex decision, evaluate tradeoffs, scope work before building, choose between competing approaches, or reason through an architectural or strategic choice before committing to it. Do NOT attempt to resolve ambiguous, high-stakes, or multi-faceted decisions by jumping straight to implementation. Use this skill to deliberate first. Trigger on: "resonera", "help me think through", "should I", "I'm torn between", "what's the right approach", "let's reason about", "help me decide", "think this through with me", "let's deliberate", "what are the tradeoffs", "scope this out", "before I build this", "talk me through", or when the user is stuck between options. Also trigger when realisera or optimera brainstorm sessions surface decisions too complex for inline resolution.