external-connector-readiness
starsforks
How to install external-connector-readiness?
rlaope/oh-my-hermes/external-connector-readiness
$npx -y skills add rlaope/oh-my-hermes --skill external-connector-readiness[omh] Hermes external connector readiness workflow: decide whether a candidate plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable enough to adopt, route, or trial.
SKILL.md
| 1 | # External Connector Readiness |
| 2 | |
| 3 | This is a Hermes-native `external-connector-readiness` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `external-connector-readiness` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: external-connector-readiness compare weather plugin and wxtrain candidates with cost, freshness, multimodal evidence, and fallback routes before adoption. |
| 20 | - Expected behavior: Produce `prepare_external_connector_readiness` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: external-connector-readiness silently enable a paid connector and claim weather, SQL, and screenshot results without observed provider evidence. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Candidate connector, target domain, read/write scope, modality needs, provider owner, fallback workflow, and stop condition are explicit. |
| 32 | - Cost, quota, credential, permission, live-data freshness, multimodal capture, safety, and compliance boundaries are marked ready, missing, risky, or not_observed. |
| 33 | - Route live read-only lookups to live-info-operator, external writes to connector-operator, datasets/SQL to data-analysis, and missing tools to toolbelt-readiness before claiming results. |
| 34 | - Provider responses, screenshots, audio/video/file captures, query outputs, message ids, and external mutations are reported only from observed trial evidence. |
| 35 | |
| 36 | ## Recovery Notes |
| 37 | |
| 38 | - If the candidate list is unknown, route to skill-scout or source-finder before readiness scoring. |
| 39 | - If credentials, cost authority, or connector installation is missing, keep readiness blocked and route setup to toolbelt-readiness. |
| 40 | - If a specific provider action is already selected, route read-only live data to live-info-operator or write/mutation tasks to connector-operator. |
| 41 | |
| 42 | ## OMH Context Rail |
| 43 | |
| 44 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 45 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 46 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 47 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 48 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 49 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 50 | - Coverage: Every generated workflow skill carries this rail. |
| 51 | - Normal users talk to Hermes; OMH CLI is infra. |
| 52 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 53 | |
| 54 | ## Use When |
| 55 | |
| 56 | Use before adopting, enabling, or routing an external plugin/connector/API when Hermes must compare capability, auth, cost, modality, freshness, safety, fallback, and observable trial evidence. |
| 57 | |
| 58 | Strong routing signals: `external-connector-readiness`, `external connector readiness`, `connector readiness matrix`, `plugin readiness matrix`, `provider readiness`, `api readiness`, `connector adoption`, `external plugin adoption`, `weather plugin readiness`, `weather connector readiness`, `wxtrain readiness`, `onequery read-only sql`, `read-only sql connector`, `sql connector readiness`, `nextcloud conne |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
