octo

AI Community v0.2.0

Skill notes

Step 1: Check auth

Has app_id/app_secret: proceed to step 2 NOT CONFIGURED: ask the user for their Octopus ApplicationKey (appId + appSecret), then:

Step 2: Init (generates template + installs skill)

This creates .claude/rules/octopus-observability.md and installs the octo skill.

Step 3: Fill in the context (YOU do this, not the user)

Read the generated template, then scan the codebase and query live Octopus data: 3a. Identify project type and find service names from code: Scan: package.json, pom.xml, docker-compose, k8s manifests Spring: application.yml → spring.application.name Frontend: @octopus-sdk/browser-rum init → applicationName

Keeping Context Fresh

The context file is a living document, not a one-time snapshot. When you're querying Octopus during any task, watch for signs that the context is stale: Unknown service: query returns data for a service not listed in the context file Topology changed: services topo shows new upstream/downstream not documented New data collection: find SDK imports (RUM, LLM, etc.) in code that aren't in the context

Query Syntax

All -q/--query options use Octopus search syntax:

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
100 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@kanyun-inc · v0.2.0 · MIT
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Node.js · Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Env read
Network behavior
Local-only
Install commands
None (reference only)
01
Step 1: Check auth

Has app_id/app_secret: proceed to step 2 NOT CONFIGURED: ask the user for their Octopus ApplicationKey (appId + appSecret), then:

02
Step 2: Init (generates template + installs skill)

This creates `.claude/rules/octopus-observability.md` and installs the octo skill.

03
Step 3: Fill in the context (YOU do this, not the user)

Read the generated template, then scan the codebase and query live Octopus data: 3a. Identify project type and find service names from code: Scan: package.json, pom.xml, docker-compose, k8s manifests Spring: `application.yml` → `spring.application.name` Frontend: `@octopus-sdk/browser-rum` init → `applicationName`

Discussion

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