본문으로 건너뛰기
cccskills
무료GitHub에 공개

agntcy-status

Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Show AGNTCY/SLIM/CASA integration status — whether the optional SLIM runtime package is installed, whether a SLIM endpoint is configured, which transport is the default, and what the agntcy mod has seen this session. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?". Read-only; makes no network call.

설치 방법 보기

이럴 때 유용합니다

  • Check whether AGNTCY is configured
  • Review SLIM package and endpoint settings
  • Inspect mod counters for the current project
  • Clarify which CASA and IOC features are implemented

포함된 파일(1)

  • SKILL.md2.2 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Report what can be measured on this machine, and say "unknown" for anything that cannot. Never invent a healthy status.

Steps

  1. Endpoint — run test -n "$RUFLO_AGNTCY_SLIM_ENDPOINT" && echo set || echo unset. Report only set or unset; do not print the value (an endpoint can carry credentials).
  2. Runtime package — run npm ls @agntcy/slim-bindings 2>&1 | tail -3 from the project root. (empty) or ERR! missing means not installed (the supported default: the package is an optionalDependency). Do not import() it from the shell; resolving a package runs its code.
  3. Active transport — local in-process transport is the default. There is no read-only transport status command: ruflo transport with no arguments only prints help, and ruflo transport use slim is a switch that contacts the configured endpoint, so do not run it just to check status. Report "local (default)" unless the user says they switched.
  4. Mod counters — Read .claude-flow/agntcy-mod/status.json if it exists (calls, blocked, guard, updatedMs). Missing file means the mod has not run in this project yet.
  5. CASA, IOC events, identity attributes — the CASA policy compiler ships in this plugin (src/casa), but runtime enforcement is not wired into the ruflo CLI (no CASA reference in v3/@claude-flow/*/src), and Layer 9 events and OTel attributes are design items in ADR-380 §§4-5. Report these as "compiler present, enforcement not wired in the CLI" and "not implemented"; do not report them as enabled.

Output

One short table: endpoint (set/unset), package (installed version or absent), transport (local/slim), mod counters, CASA/IOC/identity (state from step 5). If the endpoint is set but the package is absent, say the transport falls back to local and point to ADR-380 §1 for setup.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

adr-index

무료

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

ruvnet의 스킬 모두 보기

이 스킬의 문제 신고