agentera

AI Community

Skill notes

Shared Protocol

All capabilities reference shared primitives defined in protocol.yaml: Confidence scale: 0-100, five tiers with explicit boundaries Severity levels: finding vocabulary and issue vocabulary Visual tokens: status, severity, confidence, and trend glyphs Phase model: five phases with valid transitions

Capabilities

Capability · Primary route · Purpose ⌂ · hej · /agentera status · Orientation and routing ⛥ · visionera · /agentera vision · Define project direction ❈ · resonera · /agentera discuss · Structured deliberation ⬚ · inspirera · /agentera research · External pattern analysis

Routing Logic

When a request arrives, route to the matching capability using the five-layer routing model from Decision 42.

Prerequisite: Single-call installed CLI gate

This gate is mandatory, but the gate and the orientation dashboard source are the same installed CLI invocation. For bare /agentera or bare hej, the first normal state-access tool call is: Resolve RESOLVED_AGENTERA_HOME with the app-home precedence AGENTERA_HOME when set, otherwise the platform data home. Do not run glob, grep, read,

User-facing repair wording

Recovery and troubleshooting prompts must be plain enough for a non-technical user. Never ask the user to choose between technical install concepts, internal directory states, command-mode flags, or package-layout terms. Keep those as internal facts. User-facing copy must answer four questions in this order:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@jgabor · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: V1 migration handling

Do not perform separate v1 Markdown/YAML discovery before a normal prime briefing. The top-level CLI owns v1 detection. For bare `/agentera` or bare `hej`, render any `v1 artifacts detected` attention item and affected-file list from `agentera prime`; do not spend extra tool calls on `.agentera/*.md`, `.agentera/*.yaml`, or `VISION.md` globs.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.