원클릭으로 Manus에서 모든 스킬 실행

check-sentinel-setup

스타4

포크0

업데이트2026년 7월 13일 19:01

Run an offline Sentinel package doctor and separate local installation defects from host enablement or Roboflow sign-in problems. TRIGGER when: the user asks to check, verify, diagnose, or troubleshoot a Sentinel plugin installation; run the setup doctor; find missing skills, packaged files, or Roboflow tools; or confirm Sentinel installed correctly. SKIP when: Sentinel and Roboflow work and the user wants to count boxes or solve a CV task; the package is healthy but OAuth/sign-in alone failed (auth-setup); or the request is deployment economics/crossover only (estimate-economics).

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

Borda

Borda/vision-delivery

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Check Sentinel Setup

Diagnose setup in layers without guessing host state or copying upstream Roboflow authentication recipes.

Run the offline package check

Resolve the plugin root from this loaded skill file, then run from any working directory:

python <plugin-root>/resources/scripts/sentinel_doctor.py --json

Do not assume the current project is the plugin checkout. The doctor checks synchronized manifests, the URL-only MCP entry, packaged resources, and discoverable skills. It performs no network or account operation.

If the doctor fails, report every failed check and recommend reinstalling with the two host-specific commands in the repository quick start. Do not edit host settings automatically.

Check the host layer

After the offline status is passed:

Verify sentinel@sentinel is installed and enabled using host-visible plugin state when available.
Verify the host exposes the bundled skills and a roboflow MCP server configured at the expected URL. Never infer this from repository files alone.
Report Roboflow authorization as unverified unless an authenticated read actually succeeds in the active host.
When connection recovery is needed, load sibling ../auth-setup/SKILL.md and follow it. Do not restate a provider credential, API, or UI recipe here.

Report

Return three separate results:

package: passed|failed, with doctor evidence;
host: passed|failed|unverified, with installed/enabled evidence;
roboflow_auth: passed|failed|unverified, only from an observed host result.

Never collapse a healthy package into “fully working” while the host or authenticated service remains unverified.

이 저장소의 다른 Skills

같은 저장소

deliver-cv-project

Borda/vision-delivery

Turn an independently evaluated CV model or pipeline into a verified delivery handoff without copying volatile platform recipes. TRIGGER when: user has a working model, Workflow, OCR pipeline, or tracker and asks to export it, run locally, integrate an app/camera/RTSP source, deploy, productionize, monitor drift, add active learning, or make a runnable package. SKIP when: user asks to build a detector/model from sample images, the capability is unsolved, or measured acceptance is absent (solve-cv-task or modality skill); the request is cost/crossover only (estimate-economics); it asks only for a current Roboflow API field, UI path, model ID, or platform how-to (official Roboflow resource); or it only post-processes existing masks/data.

2026-07-134

auth-setup

Borda/vision-delivery

Connect or troubleshoot Sentinel's URL-only Roboflow MCP sign-in. TRIGGER when: the user asks to connect Roboflow, sign in, authorize OAuth, configure the plugin, or diagnose unavailable/unauthorized Roboflow MCP tools; the user asks whether a Roboflow API key is required for plugin installation. SKIP when: Roboflow MCP tools already work; the task is purely local, such as discussing a labeling approach for raw footage, and needs no Roboflow operation; a generated standalone client needs credentials (delegate its exact auth shape to the current official Roboflow API/inference skill).

2026-07-134

classify-or-flag

Borda/vision-delivery

Produce one whole-image verdict: pass/fail, category, compliance, or anomaly. TRIGGER when: user asks whether an image is defective/compliant; to flag bad parts, classify product images, run image-level quality control, detect an anomaly, or build binary/multi-class classification. SKIP when: user asks how many boxes/pallets or for other object counts or per-person PPE (detect-and-analyze); masks/area (segment-and-analyze); identity across video (track-and-count); OCR/codes (read-text); to compare self-hosting vs managed or cost only (estimate-economics); or delivery/export of a working classifier (deliver-cv-project).

2026-07-134

decision-report

Borda/vision-delivery

Generate a portable stakeholder decision report for a CV deployment decision. TRIGGER when: user explicitly asks for a decision report, manager report, or stakeholder doc after a cost crossover has been computed; phrases: "write me a decision report", "generate a report for my manager", "I need a stakeholder doc", "produce the decision doc", "decision-report skill", "report for my team". SKIP when: no cost crossover exists yet — estimate-economics must run first and deliver a crossover number; user is still in build work; user wants a one-paragraph summary (answer inline instead).

2026-07-134

decompose-to-pipeline

Borda/vision-delivery

Decompose a complex vision-and-reasoning requirement into the cheapest measurable pipeline. TRIGGER when: user asks to monitor/alert, analyze footage over time, combine perception with aggregation/reporting, determine whether something is feasible to detect (including sensor limits or smoldering), or replace repeated vision-language calls with a cheaper system. SKIP when: the request is single-frame detection/counting (detect-and-analyze), whole-image classification (classify-or-flag), deployment cost only (estimate-economics), or the pipeline is already working and needs delivery (deliver-cv-project).

2026-07-134

detect-and-analyze

Borda/vision-delivery

Detect instances and analyze boxes, counts, crops, regions, or metadata. TRIGGER when: user asks to count/detect objects, report the number of defects, build a model that counts trucks, tally boxes/pallets on a conveyor, find workers lacking PPE, crop detections, extract an ROI, estimate box-relative size, or report per-object confidence/zone metadata. SKIP when: user needs one whole-image verdict (classify-or-flag); identity/path/dwell/line crossing (track-and-count); masks/contours/calibrated area/crack width (segment-and-analyze); OCR/serials (read-text); to compare self-hosting vs managed or cost only (estimate-economics); active learning/export/delivery of a working model (deliver-cv-project).

2026-07-134

name

check-sentinel-setup

description

Check Sentinel Setup

Diagnose setup in layers without guessing host state or copying upstream Roboflow authentication recipes.

Run the offline package check

Resolve the plugin root from this loaded skill file, then run from any working directory:

python <plugin-root>/resources/scripts/sentinel_doctor.py --json

If the doctor fails, report every failed check and recommend reinstalling with the two host-specific commands in the repository quick start. Do not edit host settings automatically.

Check the host layer

After the offline status is passed:

Verify sentinel@sentinel is installed and enabled using host-visible plugin state when available.
Verify the host exposes the bundled skills and a roboflow MCP server configured at the expected URL. Never infer this from repository files alone.
Report Roboflow authorization as unverified unless an authenticated read actually succeeds in the active host.
When connection recovery is needed, load sibling ../auth-setup/SKILL.md and follow it. Do not restate a provider credential, API, or UI recipe here.

Report

Return three separate results:

package: passed|failed, with doctor evidence;
host: passed|failed|unverified, with installed/enabled evidence;
roboflow_auth: passed|failed|unverified, only from an observed host result.

Never collapse a healthy package into “fully working” while the host or authenticated service remains unverified.