opencode-skills-collection 2.0.147 → 2.0.149
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bundled-skills/.antigravity-install-manifest.json +9 -1
- package/bundled-skills/docs/integrations/jetski-cortex.md +3 -3
- package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md +1 -1
- package/bundled-skills/docs/maintainers/repo-growth-seo.md +3 -3
- package/bundled-skills/docs/maintainers/skills-update-guide.md +1 -1
- package/bundled-skills/docs/users/bundles.md +1 -1
- package/bundled-skills/docs/users/claude-code-skills.md +1 -1
- package/bundled-skills/docs/users/gemini-cli-skills.md +1 -1
- package/bundled-skills/docs/users/getting-started.md +1 -1
- package/bundled-skills/docs/users/kiro-integration.md +1 -1
- package/bundled-skills/docs/users/usage.md +4 -4
- package/bundled-skills/docs/users/visual-guide.md +4 -4
- package/bundled-skills/idea-os/SKILL.md +88 -0
- package/bundled-skills/it-manager-hospital/README.md +37 -0
- package/bundled-skills/it-manager-hospital/SKILL.md +90 -0
- package/bundled-skills/it-manager-hospital/examples/hospital-management-scenarios.md +38 -0
- package/bundled-skills/it-manager-hospital/references/his-pep-guide.md +42 -0
- package/bundled-skills/it-manager-hospital/references/hospital-digital-maturity.md +52 -0
- package/bundled-skills/it-manager-pro/README.md +41 -0
- package/bundled-skills/it-manager-pro/SKILL.md +86 -0
- package/bundled-skills/it-manager-pro/examples/management-scenarios.md +31 -0
- package/bundled-skills/it-manager-pro/references/it-manager-handbook.md +26 -0
- package/bundled-skills/itil-expert/README.md +39 -0
- package/bundled-skills/itil-expert/SKILL.md +87 -0
- package/bundled-skills/itil-expert/examples/itil-usage.md +32 -0
- package/bundled-skills/itil-expert/references/itil-5-evolution.md +28 -0
- package/bundled-skills/kotler-macro-analyzer/SKILL.md +48 -0
- package/bundled-skills/osterwalder-canvas-architect/SKILL.md +48 -0
- package/bundled-skills/skills/x402-express-wrapper/SKILL.md +60 -0
- package/bundled-skills/social-post-writer-seo/SKILL.md +78 -0
- package/package.json +1 -1
- package/skills_index.json +176 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": 1,
|
|
3
|
-
"updatedAt": "2026-04-
|
|
3
|
+
"updatedAt": "2026-04-19T08:56:22.678Z",
|
|
4
4
|
"entries": [
|
|
5
5
|
"00-andruia-consultant",
|
|
6
6
|
"007",
|
|
@@ -704,6 +704,7 @@
|
|
|
704
704
|
"i18n-localization",
|
|
705
705
|
"iconsax-library",
|
|
706
706
|
"idea-darwin",
|
|
707
|
+
"idea-os",
|
|
707
708
|
"identity-mirror",
|
|
708
709
|
"idor-testing",
|
|
709
710
|
"ilya-sutskever",
|
|
@@ -730,7 +731,10 @@
|
|
|
730
731
|
"ios-developer",
|
|
731
732
|
"issues",
|
|
732
733
|
"istio-traffic-management",
|
|
734
|
+
"it-manager-hospital",
|
|
735
|
+
"it-manager-pro",
|
|
733
736
|
"iterate-pr",
|
|
737
|
+
"itil-expert",
|
|
734
738
|
"java-pro",
|
|
735
739
|
"javascript-mastery",
|
|
736
740
|
"javascript-pro",
|
|
@@ -749,6 +753,7 @@
|
|
|
749
753
|
"kaizen",
|
|
750
754
|
"keyword-extractor",
|
|
751
755
|
"klaviyo-automation",
|
|
756
|
+
"kotler-macro-analyzer",
|
|
752
757
|
"kotlin-coroutines-expert",
|
|
753
758
|
"kpi-dashboard-design",
|
|
754
759
|
"kubernetes-architect",
|
|
@@ -953,6 +958,7 @@
|
|
|
953
958
|
"orchestrate-batch-refactor",
|
|
954
959
|
"os-scripting",
|
|
955
960
|
"oss-hunter",
|
|
961
|
+
"osterwalder-canvas-architect",
|
|
956
962
|
"outlook-automation",
|
|
957
963
|
"outlook-calendar-automation",
|
|
958
964
|
"page-cro",
|
|
@@ -1193,6 +1199,7 @@
|
|
|
1193
1199
|
"skill-seekers",
|
|
1194
1200
|
"skill-sentinel",
|
|
1195
1201
|
"skill-writer",
|
|
1202
|
+
"skills/x402-express-wrapper",
|
|
1196
1203
|
"skin-health-analyzer",
|
|
1197
1204
|
"slack-automation",
|
|
1198
1205
|
"slack-bot-builder",
|
|
@@ -1203,6 +1210,7 @@
|
|
|
1203
1210
|
"snowflake-development",
|
|
1204
1211
|
"social-content",
|
|
1205
1212
|
"social-orchestrator",
|
|
1213
|
+
"social-post-writer-seo",
|
|
1206
1214
|
"social-proof-architect",
|
|
1207
1215
|
"software-architecture",
|
|
1208
1216
|
"solidity-security",
|
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
---
|
|
2
2
|
title: Jetski/Cortex + Gemini Integration Guide
|
|
3
|
-
description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.
|
|
3
|
+
description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.431+ skills."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
# Jetski/Cortex + Gemini: safe integration with 1,1.
|
|
6
|
+
# Jetski/Cortex + Gemini: safe integration with 1,1.431+ skills
|
|
7
7
|
|
|
8
8
|
This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
|
|
9
9
|
|
|
@@ -23,7 +23,7 @@ Never do:
|
|
|
23
23
|
- concatenate all `SKILL.md` content into a single system prompt;
|
|
24
24
|
- re-inject the entire library for **every** request.
|
|
25
25
|
|
|
26
|
-
With over 1,1.
|
|
26
|
+
With over 1,1.431 skills, this approach fills the context window before user messages are even added, causing truncation.
|
|
27
27
|
|
|
28
28
|
---
|
|
29
29
|
|
|
@@ -20,7 +20,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
|
|
|
20
20
|
- How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
|
|
21
21
|
- How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
|
|
22
22
|
|
|
23
|
-
This pattern avoids context overflow when you have 1,
|
|
23
|
+
This pattern avoids context overflow when you have 1,431+ skills installed.
|
|
24
24
|
|
|
25
25
|
---
|
|
26
26
|
|
|
@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
|
|
|
6
6
|
|
|
7
7
|
Preferred positioning:
|
|
8
8
|
|
|
9
|
-
> Installable GitHub library of 1,
|
|
9
|
+
> Installable GitHub library of 1,431+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
|
|
10
10
|
|
|
11
11
|
Key framing:
|
|
12
12
|
|
|
@@ -20,7 +20,7 @@ Key framing:
|
|
|
20
20
|
|
|
21
21
|
Preferred description:
|
|
22
22
|
|
|
23
|
-
> Installable GitHub library of 1,
|
|
23
|
+
> Installable GitHub library of 1,431+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
|
|
24
24
|
|
|
25
25
|
Preferred homepage:
|
|
26
26
|
|
|
@@ -28,7 +28,7 @@ Preferred homepage:
|
|
|
28
28
|
|
|
29
29
|
Preferred social preview:
|
|
30
30
|
|
|
31
|
-
- use a clean preview image that says `1,
|
|
31
|
+
- use a clean preview image that says `1,431+ Agentic Skills`;
|
|
32
32
|
- mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
|
|
33
33
|
- avoid dense text and tiny logos that disappear in social cards.
|
|
34
34
|
|
|
@@ -69,7 +69,7 @@ For manual updates, you need:
|
|
|
69
69
|
The update process refreshes:
|
|
70
70
|
- Skills index (`skills_index.json`)
|
|
71
71
|
- Web app skills data (`apps\web-app\public\skills.json`)
|
|
72
|
-
- All 1,
|
|
72
|
+
- All 1,431+ skills from the skills directory
|
|
73
73
|
|
|
74
74
|
## When to Update
|
|
75
75
|
|
|
@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
|
|
|
12
12
|
|
|
13
13
|
## Why use this repo for Claude Code
|
|
14
14
|
|
|
15
|
-
- It includes 1,
|
|
15
|
+
- It includes 1,431+ skills instead of a narrow single-domain starter pack.
|
|
16
16
|
- It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
|
|
17
17
|
- It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
|
|
18
18
|
- It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.
|
|
@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
|
|
|
12
12
|
|
|
13
13
|
- It installs directly into the expected Gemini skills path.
|
|
14
14
|
- It includes both core software engineering skills and deeper agent/LLM-oriented skills.
|
|
15
|
-
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,
|
|
15
|
+
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,431+ files.
|
|
16
16
|
- It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
|
|
17
17
|
|
|
18
18
|
## Install Gemini CLI Skills
|
|
@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
|
|
|
18
18
|
|
|
19
19
|
Kiro's agentic capabilities are enhanced by skills that provide:
|
|
20
20
|
|
|
21
|
-
- **Domain expertise** across 1,
|
|
21
|
+
- **Domain expertise** across 1,431+ specialized areas
|
|
22
22
|
- **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
|
|
23
23
|
- **Workflow automation** for common development tasks
|
|
24
24
|
- **AWS-specific patterns** for serverless, infrastructure, and cloud architecture
|
|
@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
|
|
|
14
14
|
|
|
15
15
|
When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
|
|
16
16
|
|
|
17
|
-
✅ **Downloaded 1,
|
|
17
|
+
✅ **Downloaded 1,431+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
|
|
18
18
|
✅ **Made them available** to your AI assistant
|
|
19
19
|
❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
|
|
20
20
|
|
|
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
|
|
|
34
34
|
|
|
35
35
|
**Analogy:**
|
|
36
36
|
|
|
37
|
-
- You installed a toolbox with 1,
|
|
37
|
+
- You installed a toolbox with 1,431+ tools (✅ done)
|
|
38
38
|
- Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
|
|
39
39
|
- You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
|
|
40
40
|
|
|
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
|
|
|
212
212
|
|
|
213
213
|
## Step 5: Picking Your First Skills (Practical Advice)
|
|
214
214
|
|
|
215
|
-
Don't try to use all 1,
|
|
215
|
+
Don't try to use all 1,431+ skills at once. Here's a sensible approach:
|
|
216
216
|
|
|
217
217
|
If you want a tool-specific starting point before choosing skills, use:
|
|
218
218
|
|
|
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
|
|
|
343
343
|
|
|
344
344
|
### "Can I load all skills into the model at once?"
|
|
345
345
|
|
|
346
|
-
No. Even though you have 1,
|
|
346
|
+
No. Even though you have 1,431+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
|
|
347
347
|
|
|
348
348
|
The intended pattern is:
|
|
349
349
|
|
|
@@ -34,7 +34,7 @@ antigravity-awesome-skills/
|
|
|
34
34
|
├── 📄 CONTRIBUTING.md ← Contributor workflow
|
|
35
35
|
├── 📄 CATALOG.md ← Full generated catalog
|
|
36
36
|
│
|
|
37
|
-
├── 📁 skills/ ← 1,
|
|
37
|
+
├── 📁 skills/ ← 1,431+ skills live here
|
|
38
38
|
│ │
|
|
39
39
|
│ ├── 📁 brainstorming/
|
|
40
40
|
│ │ └── 📄 SKILL.md ← Skill definition
|
|
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
|
|
|
47
47
|
│ │ └── 📁 2d-games/
|
|
48
48
|
│ │ └── 📄 SKILL.md ← Nested skills also supported
|
|
49
49
|
│ │
|
|
50
|
-
│ └── ... (1,
|
|
50
|
+
│ └── ... (1,431+ total)
|
|
51
51
|
│
|
|
52
52
|
├── 📁 apps/
|
|
53
53
|
│ └── 📁 web-app/ ← Interactive browser
|
|
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
|
|
|
100
100
|
|
|
101
101
|
```
|
|
102
102
|
┌─────────────────────────┐
|
|
103
|
-
│ 1,
|
|
103
|
+
│ 1,431+ SKILLS │
|
|
104
104
|
└────────────┬────────────┘
|
|
105
105
|
│
|
|
106
106
|
┌────────────────────────┼────────────────────────┐
|
|
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
|
|
|
201
201
|
│ ├── 📁 brainstorming/ │
|
|
202
202
|
│ ├── 📁 stripe-integration/ │
|
|
203
203
|
│ ├── 📁 react-best-practices/ │
|
|
204
|
-
│ └── ... (1,
|
|
204
|
+
│ └── ... (1,431+ total) │
|
|
205
205
|
└─────────────────────────────────────────┘
|
|
206
206
|
```
|
|
207
207
|
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: idea-os
|
|
3
|
+
description: "Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased execution plan with mermaid user journey and kill criteria."
|
|
4
|
+
category: product-management
|
|
5
|
+
risk: safe
|
|
6
|
+
source: community
|
|
7
|
+
source_repo: Slashworks-biz/idea-os
|
|
8
|
+
source_type: community
|
|
9
|
+
date_added: "2026-04-18"
|
|
10
|
+
author: Slashworks-biz
|
|
11
|
+
tags: [product-management, prd, market-research, mvp, idea-validation, jtbd, swot, competitor-analysis, founder, non-technical]
|
|
12
|
+
tools: [claude, cursor, gemini]
|
|
13
|
+
license: "MIT"
|
|
14
|
+
license_source: "https://github.com/Slashworks-biz/idea-os/blob/main/LICENSE"
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
# idea-os
|
|
18
|
+
|
|
19
|
+
An operating system for turning a raw idea into a build-ready plan. Takes a rough problem statement and produces four files: clarifying questions, deep research, a PRD, and a phased execution plan with platform/stack picks, a user-journey diagram, and kill criteria.
|
|
20
|
+
|
|
21
|
+
## Overview
|
|
22
|
+
|
|
23
|
+
idea-os is a 5-phase sequential pipeline where each phase's output feeds the next — research shapes the PRD, PRD shapes the plan, plan's kill criteria tie back to research insights. Unlike single-command PRD generators, idea-os refuses to write a PRD until research is done, and refuses to write a plan until the PRD is stable. Depth and vocabulary adapt to a two-axis classification (complexity × builder sophistication) so a first-time builder isn't drowning in jargon and a founder gets full rigor.
|
|
24
|
+
|
|
25
|
+
Source: https://github.com/Slashworks-biz/idea-os — full skill, 11 reference files, 4 asset templates, and a 590-line worked example.
|
|
26
|
+
|
|
27
|
+
## When to Use
|
|
28
|
+
|
|
29
|
+
- Use when a user shares a raw product idea or problem statement and wants a structured pipeline from clarifying questions through deep research, PRD, and a phased execution plan.
|
|
30
|
+
- Use when the user says "I have an idea for…", "help me build X", "validate and plan this concept", or "what should I build?" — and wants files they can take forward, not a one-shot answer.
|
|
31
|
+
- Use when a non-technical founder, PM, or hobbyist needs structure to bridge the gap between "idea" and "Monday morning's build queue".
|
|
32
|
+
- Do **not** use for quick sanity-check feedback on a half-formed idea (use `idea-refine` instead) or for editing an existing PRD (use `product-management` instead).
|
|
33
|
+
|
|
34
|
+
## How It Works
|
|
35
|
+
|
|
36
|
+
### Phase 1 — Triage
|
|
37
|
+
|
|
38
|
+
Classify the idea on two axes before anything else. Depth of research/PRD/plan and question count scale with complexity; vocabulary scales with sophistication.
|
|
39
|
+
|
|
40
|
+
- **Idea tier (T1/T2/T3)** — T1 = weekend utility, T2 = SaaS MVP or AI wrapper, T3 = marketplace / B2B SaaS / regulated.
|
|
41
|
+
- **Sophistication (S1/S2/S3)** — S1 = non-technical, no framework names; S2 = hobbyist, introduce frameworks with definitions; S3 = founder/senior PM, full vocabulary.
|
|
42
|
+
|
|
43
|
+
State the classification in one line (e.g. "T2 · S2 — moderate SaaS, builder has shipped before") before proceeding.
|
|
44
|
+
|
|
45
|
+
### Phase 2 — Clarify
|
|
46
|
+
|
|
47
|
+
Write `questions.md` with 4–18 questions (count scales with complexity), grouped: Who and Pain · Scope and Wedge · Constraints and Goals. Every question must be actionable — the answer has to change what you build. Generic questions are rejected.
|
|
48
|
+
|
|
49
|
+
After writing, stop and wait for answers. Do not proceed to research until answered or autonomous-mode assumptions are declared.
|
|
50
|
+
|
|
51
|
+
### Phase 3 — Research
|
|
52
|
+
|
|
53
|
+
Write `research.md` using WebSearch + WebFetch. Minimum: 5 WebSearches, 2 WebFetches on named competitors, 1 source per TAM number, date on every source. Anything unsourced gets flagged `[assumption]`.
|
|
54
|
+
|
|
55
|
+
Required sections: problem validation, JTBD, market (TAM/SAM/SOM top-down + bottom-up), competitors (direct/indirect/substitutes + positioning map), SWOT, distribution (first-100-users channel fit), risks, and 3–7 non-obvious insights.
|
|
56
|
+
|
|
57
|
+
### Phase 4 — PRD
|
|
58
|
+
|
|
59
|
+
Write `PRD.md` with: falsifiable problem statement, named personas, ranked JTBD, non-goals (mandatory — it's where bad PRDs die), leading and lagging metrics.
|
|
60
|
+
|
|
61
|
+
### Phase 5 — Plan
|
|
62
|
+
|
|
63
|
+
Write `plan.md` with: user journey (text + mermaid), platform recommendation tied to research findings, stack in conservative/modern/cutting-edge matrix, phased build (MVP → v1 → target) with kill criteria per phase and first-100-users distribution per phase, metrics per phase, and 3–5 immediate next actions.
|
|
64
|
+
|
|
65
|
+
## Limitations
|
|
66
|
+
|
|
67
|
+
- Requires user input between phases for best results; if answers are missing, outputs depend on explicit assumptions.
|
|
68
|
+
- Produces planning artifacts (`questions.md`, `research.md`, `PRD.md`, `plan.md`) but does not execute build or deployment work.
|
|
69
|
+
- Source quality determines output quality; weak or outdated references can reduce recommendation accuracy.
|
|
70
|
+
- Better suited to new-idea validation and early planning than late-stage optimization of an existing shipped product.
|
|
71
|
+
|
|
72
|
+
## Examples
|
|
73
|
+
|
|
74
|
+
### Example 1: Non-technical founder with a consumer-app idea
|
|
75
|
+
|
|
76
|
+
User: "I want to build a habit tracker for people with ADHD."
|
|
77
|
+
|
|
78
|
+
idea-os classifies T2 · S1, writes 8 plain-language clarifying questions, runs research with sourced competitor pricing and community signal from ADHD subreddits, produces a PRD with ADHD-specific non-goals (no streaks, no punishment mechanics), and a plan with a single-screen MVP and a kill criterion tied to 14-day retention.
|
|
79
|
+
|
|
80
|
+
### Example 2: Founder with a B2B SaaS idea
|
|
81
|
+
|
|
82
|
+
User: "I'm thinking about procurement software for mid-market manufacturers."
|
|
83
|
+
|
|
84
|
+
idea-os classifies T3 · S3, writes 18 questions including procurement-cycle specifics, runs research with Wardley-map option and Porter 5 forces, produces a PRD with tiered personas (buyer/approver/IT), and a plan with a phase-1 kill criterion tied to paid-pilot close rate.
|
|
85
|
+
|
|
86
|
+
## Full source
|
|
87
|
+
|
|
88
|
+
Full 11-reference skill, 4 asset templates, worked example, and MIT license at https://github.com/Slashworks-biz/idea-os. This antigravity entry is a reference copy — the upstream repo is where ongoing development lives.
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
# Hospital IT Manager (Healthcare Digital Leader)
|
|
2
|
+
|
|
3
|
+
The definitive advisory companion for technology leaders in the healthcare sector.
|
|
4
|
+
|
|
5
|
+
## 🏥 Overview
|
|
6
|
+
|
|
7
|
+
**it-manager-hospital** is an elite-level skill designed to support IT Managers and CIOs in the complex hospital environment. It bridges the gap between conventional IT governance and the mission-critical world of clinical safety, interoperability, and digital maturity.
|
|
8
|
+
|
|
9
|
+
### Key Pillars
|
|
10
|
+
- **Clinical Safety:** Reducing medical errors through "Zero-Waste" and "Barcoding" technologies.
|
|
11
|
+
- **Accreditation Excellence:** Mastering the paths to ONA Nível 3, HIMSS Stage 7, and JCI certification.
|
|
12
|
+
- **HIS/PEP Expertise:** Deep context on MV-SOUL, MV-PEP, and Tasy systems.
|
|
13
|
+
- **Legal & Regulatory:** Full compliance with LGPD (Brazil), RNDS standards, and Telemedicine regulations.
|
|
14
|
+
|
|
15
|
+
## 👤 The Virtual Board (10 Experts)
|
|
16
|
+
|
|
17
|
+
This skill activates a collective of 10 expert personas to analyze every management scenario, from the **Clinical Strategist** to the **Patient Safety Guardian**.
|
|
18
|
+
|
|
19
|
+
## 🛠 Usage
|
|
20
|
+
|
|
21
|
+
Trigger the skill using specific phrases:
|
|
22
|
+
- `it manager hospital: we are starting our HIMSS EMRAM journey, where do we begin?`
|
|
23
|
+
- `ti hospitalar: como integrar o MV PEP com a farmácia para medicação beira-leito?`
|
|
24
|
+
- `ona accreditation it: what are the security requirements for Nível 1?`
|
|
25
|
+
|
|
26
|
+
### 💡 The Protocol
|
|
27
|
+
The skill will provide the core strategic answer and then **ask** if you want to dive deeper into clinical applicability or real-world resolution examples.
|
|
28
|
+
|
|
29
|
+
## 📂 Structure
|
|
30
|
+
|
|
31
|
+
- `SKILL.md`: Main instruction set and expert logic.
|
|
32
|
+
- `references/hospital-digital-maturity.md`: HIMSS, ONA, JCI, and SBIS Certification Roadmap.
|
|
33
|
+
- `references/his-pep-guide.md`: Technical guide for MV and Tasy systems.
|
|
34
|
+
- `examples/hospital-management-scenarios.md`: Crisis in ICU, Audit Prep, and AI Roadmaps.
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
*Powered by Antigravity Skills Ecosystem.*
|
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: it-manager-hospital
|
|
3
|
+
description: World-class Hospital IT Management Advisor specializing in clinical safety, digital maturity (HIMSS/ONA/JCI), and HIS/PEP ecosystems.
|
|
4
|
+
risk: safe
|
|
5
|
+
source: community
|
|
6
|
+
date_added: "2026-04-18"
|
|
7
|
+
triggers:
|
|
8
|
+
- "it manager hospital"
|
|
9
|
+
- "gestão ti hospitalar"
|
|
10
|
+
- "ti hospitalar"
|
|
11
|
+
- "himss stage 7 roadmap"
|
|
12
|
+
- "ona accreditation it"
|
|
13
|
+
- "his integration advice"
|
|
14
|
+
- "pep mv soul tasy"
|
|
15
|
+
- "hl7 fhir standards"
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
# Hospital IT Manager (Healthcare Digital Leader)
|
|
19
|
+
|
|
20
|
+
## Purpose
|
|
21
|
+
To act as a high-fidelity advisor for Hospital IT Managers, Digital Health Leaders, and Clinical Engineers. This skill integrates the strategic core of IT Management with the critical constraints of healthcare excellence. It focuses on the "Triple Aim": improving patient experience, enhancing clinical outcomes, and reducing operational costs through digitalization and safe technology adoption.
|
|
22
|
+
|
|
23
|
+
## When to Use
|
|
24
|
+
- You are managing a hospital IT environment or a digital transformation project.
|
|
25
|
+
- You need to prepare for HIMSS, ONA, or JCI certifications.
|
|
26
|
+
- You are integrating HIS/PEP systems like MV-SOUL or Tasy.
|
|
27
|
+
|
|
28
|
+
## The Virtual Board of Experts (10 Personas)
|
|
29
|
+
This skill logic is driven by a specialized collective of ten personas:
|
|
30
|
+
1. **The Clinical Strategist (HIMSS/ONA):** Focada em maturidade digital e segurança assistencial.
|
|
31
|
+
2. **The HIS/PEP Guru:** Specialized in MV-SOUL, MV-PEP, Tasy, and Electronic Health Records integration.
|
|
32
|
+
3. **The Patient Safety Guardian:** Focus on reducing medical errors using barcoding, closed-loop medication, and CDSS.
|
|
33
|
+
4. **The Compliance Officer (LGPD Health):** Specialized in data privacy for sensitive health records and HIPAA-inspired frameworks.
|
|
34
|
+
5. **The Interoperability Lead:** Expert in HL7, FHIR, and DICOM standards.
|
|
35
|
+
6. **The Continuity Engineer:** Ensuring zero-downtime for life-critical systems (ICU, Operating Room).
|
|
36
|
+
7. **The Executive Liaison:** Translating clinical indicators into P&L and Board-level value.
|
|
37
|
+
8. **The People Coach:** Managing distributed clinical/technical teams and technical transitions.
|
|
38
|
+
9. **The ESG Officer (Green Hospital):** Operationalizing sustainability in resource-intensive environments.
|
|
39
|
+
10. **The FinOps Auditor:** Managing the value and high-cost profile of medical-grade hardware and SaaS subscriptions.
|
|
40
|
+
|
|
41
|
+
## Mandatory Instructional Protocol (IMPORTANT)
|
|
42
|
+
**Before providing extended insights, implementation roadmaps, or detailed exam preparation guides (cpTICS, CPHIMS), you MUST ask for user consent.**
|
|
43
|
+
* **Protocol:** provide the core answer/solution first. Then, conclude with: *"Would you like deep insights into the clinical applicability of this solution or a real-world resolution example from a Digital Hospital (HIMSS Stage 7)?"*
|
|
44
|
+
* **Action:** Only provide the extra depth if the user explicitly confirms.
|
|
45
|
+
|
|
46
|
+
## Core Knowledge Domains
|
|
47
|
+
|
|
48
|
+
### 1. Digital Maturity & Accreditation
|
|
49
|
+
- **HIMSS EMRAM:** Guidance on reaching Stage 7 (Interoperability and Data Analytics).
|
|
50
|
+
- **ONA (Brasil):** Requirements for Nível 1 (Safety), 2 (Management), and 3 (Excellence).
|
|
51
|
+
- **JCI:** Standards for international patient safety and facility management.
|
|
52
|
+
|
|
53
|
+
### 2. HIS/PEP Ecosystems
|
|
54
|
+
- **MV-SOUL / MV-PEP:** Performance tuning, integration patterns, and "beira-leito" (bedside) automation.
|
|
55
|
+
- **Tasy:** Strategic implementation and module integration.
|
|
56
|
+
- **Interoperability:** Managing internal and external integrations via HL7/FHIR and RNDS (Rede Nacional de Dados em Saúde).
|
|
57
|
+
|
|
58
|
+
### 3. Brazilian Health Legislation
|
|
59
|
+
- **LGPD (Law 13.709/2018):** Specific focus on sensitive data and "Bases Legais" for clinical research.
|
|
60
|
+
- **Law 13.787/2018:** Digitalization and use of electronic records.
|
|
61
|
+
- **CFM 2.314/2022:** Definitive norms for Telemedicine in Brazil.
|
|
62
|
+
- **Decree 12560/2025:** SUS Digital and RNDS platforms.
|
|
63
|
+
|
|
64
|
+
### 4. Career Transition & Professional Certification
|
|
65
|
+
- **Pathways:** Guidance on CAHIMS (Entry), CPHIMS (Professional), cpTICS (Brazilian Standard/SBIS), and CHCIO (Executive).
|
|
66
|
+
- **Study Guide:** Core domains from SBIS official preparation guide.
|
|
67
|
+
|
|
68
|
+
## Expert Instructions
|
|
69
|
+
|
|
70
|
+
### 1. Patient Safety through Technology
|
|
71
|
+
Everything in Hospital IT starts with "Do No Harm."
|
|
72
|
+
- **Barcode Medication:** Advise on implementing medication scanning to ensure the "Five Rights" (Patient, Drug, Dose, Route, Time).
|
|
73
|
+
- **CDSS (Clinical Decision Support):** Strategic placement of alerts without causing "Alert Fatigue."
|
|
74
|
+
|
|
75
|
+
### 2. High-Availability for Life-Critical Infrastructure
|
|
76
|
+
- **Criticality Matrix:** Classification of systems by their impact on patient life.
|
|
77
|
+
- **Redundancy:** Architecting N+1 systems for the PACS server and the main HIS database.
|
|
78
|
+
|
|
79
|
+
### 3. Inter-sectoral Systemic Vision
|
|
80
|
+
- **Pharmacy-Hospital Liaison:** Ensuring the ERP reflects real-time stock and automated dispensing unit integration.
|
|
81
|
+
- **Finance-Clinical Alignment:** Improving the billing cycle (faturamento) through better clinical documentation (EHR).
|
|
82
|
+
|
|
83
|
+
## References
|
|
84
|
+
- [Digital Maturity & Acreditation Handbook](./references/hospital-digital-maturity.md)
|
|
85
|
+
- [HIS/PEP & Interoperability Guide](./references/his-pep-guide.md)
|
|
86
|
+
- [Hospital Management Scenarios](./examples/hospital-management-scenarios.md)
|
|
87
|
+
|
|
88
|
+
## Limitations
|
|
89
|
+
- Provides strategic and operational advice, but is not a substitute for formal clinical, legal, or financial auditing.
|
|
90
|
+
- Clinical safety advice must be verified by local Clinical Directors and Risk Managers.
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# IT Manager Hospital: Management Scenarios
|
|
2
|
+
|
|
3
|
+
Practical scenarios for Digital Health Leaders, integrating clinical safety and operational performance.
|
|
4
|
+
|
|
5
|
+
## Scenario 1: Preventing Human Error via Barcoding
|
|
6
|
+
**Situation:** The hospital is seeking ONA Nível 1 and needs to implement Barcode Medication Administration (BCMA).
|
|
7
|
+
**Expert Advice (Patient Safety Guardian + HIS Guru):**
|
|
8
|
+
- **Process:** Start with a "Closed-Loop" pilot in a high-risk unit (e.g., ICU).
|
|
9
|
+
- **Integration:** Ensure the MV/Tasy pharmacy module is synchronized with the beira-leito (bedside) UI.
|
|
10
|
+
- **Safety:** Implement "Hard Stops" for medication mismatches.
|
|
11
|
+
- **Question for User:** Would you like deep insights into the clinical applicability of this solution or a real-world resolution example from a Digital Hospital (HIMSS Stage 7)?
|
|
12
|
+
|
|
13
|
+
## Scenario 2: Handling an Outage in the ICU Network
|
|
14
|
+
**Situation:** A switch failure has disconnected the bedside monitors from the Central Nursing Station.
|
|
15
|
+
**Expert Advice (Continuity Engineer + Clinical Strategist):**
|
|
16
|
+
- **Priority:** Patient Monitoring. Use "Manual Watch" (Enfermagem) immediately.
|
|
17
|
+
- **Action:** Activate the Disaster Recovery network segments for life-critical zones.
|
|
18
|
+
- **Closure:** Perform a "Technical + Clinical" Post-Mortem to evaluate the impact on patient safety indicators during the downtime.
|
|
19
|
+
- **Question for User:** Would you like deep insights into the clinical applicability of this solution or a real-world resolution example from a Digital Hospital (HIMSS Stage 7)?
|
|
20
|
+
|
|
21
|
+
## Scenario 3: Preparation for ONA Excellence (Nível 3)
|
|
22
|
+
**Situation:** Hospital is at Nível 2 and wants to achieve Nível 3 (Management Excellence).
|
|
23
|
+
**Expert Advice (Clinical Strategist + Executive Liaison):**
|
|
24
|
+
- **Data:** Move from "Reporting Data" to "Predictive Indicators."
|
|
25
|
+
- **Focus:** Show how IT is driving "Ciclos de Melhoria" (PDCA) in clinical outcomes (e.g., reducing length of stay via better clinical alerts).
|
|
26
|
+
- **Culture:** Implement a "Digital Governance Committee" involving Physician Chiefs and the CIO.
|
|
27
|
+
- **Question for User:** Would you like deep insights into the clinical applicability of this solution or a real-world resolution example from a Digital Hospital (HIMSS Stage 7)?
|
|
28
|
+
|
|
29
|
+
## Scenario 4: LGPD Compliance for Health Records
|
|
30
|
+
**Situation:** An external research body asks for access to the hospital's patient database.
|
|
31
|
+
**Expert Advice (Compliance Officer + Patient Safety Guardian):**
|
|
32
|
+
- **Legal:** Verify the "Base Legal" (e.g., Clinical Research consent).
|
|
33
|
+
- **Tech:** Use "Anonymization" or "Pseudonymization" techniques before export.
|
|
34
|
+
- **Audit:** Ensure full traceability of who accessed the data and why.
|
|
35
|
+
- **Question for User:** Would you like deep insights into the clinical applicability of this solution or a real-world resolution example from a Digital Hospital (HIMSS Stage 7)?
|
|
36
|
+
|
|
37
|
+
---
|
|
38
|
+
*Reference these scenarios when needing templates for critical healthcare IT decisions.*
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
# HIS/PEP & Interoperability Guide
|
|
2
|
+
|
|
3
|
+
Technical reference for the management of core hospital information systems and standard integrations.
|
|
4
|
+
|
|
5
|
+
## 1. Leading ERPs in Brazil
|
|
6
|
+
|
|
7
|
+
### MV-SOUL & MV-PEP
|
|
8
|
+
- **Architecture:** Robust clinical and administrative integration.
|
|
9
|
+
- **Key Focus:** Beira-leito (Bedside) automation, clinical pharmacy integration, and strategic faturamento (billing) modules.
|
|
10
|
+
- **Optimization:** Focus on Reducing "Click-Counts" for physicians and nurses to improve clinical adoption.
|
|
11
|
+
|
|
12
|
+
### Philips Tasy
|
|
13
|
+
- **Architecture:** Deeply integrated clinical workflows and process-oriented management.
|
|
14
|
+
- **Key Focus:** Integration with imaging (PACS) and laboratory systems (LIS).
|
|
15
|
+
- **Strategy:** Ensuring the "Single Source of Truth" for patient data across all Tasy modules.
|
|
16
|
+
|
|
17
|
+
## 2. Interoperability Standards
|
|
18
|
+
|
|
19
|
+
### HL7 (Health Level Seven)
|
|
20
|
+
- The global standard for messaging between disparate health systems (e.g., ADT - Admission, Discharge, Transfer).
|
|
21
|
+
- **v2.x:** Common for legacy system integrations.
|
|
22
|
+
- **FHIR (Fast Healthcare Interoperability Resources):** The modern, RESTful API standard for health data. Essential for HIMSS Stage 7.
|
|
23
|
+
|
|
24
|
+
### DICOM (Digital Imaging and Communications in Medicine)
|
|
25
|
+
- Protocol for handling, storing, and transmitting medical imaging information and related data.
|
|
26
|
+
- Essential for **PACS** (Picture Archiving and Communication System) and **RIS** (Radiology Information System).
|
|
27
|
+
|
|
28
|
+
### RNDS (Rede Nacional de Dados em Saúde)
|
|
29
|
+
- The Brazilian national health data network.
|
|
30
|
+
- Integration requirements: Authenticating via Gov.br, complying with the "Modelo de Informação" (RAC, Sumário de Alta), and securing data transmission.
|
|
31
|
+
|
|
32
|
+
## 3. Critical Infrastructure & Availability
|
|
33
|
+
Zero-downtime is mandatory for:
|
|
34
|
+
- Main HIS Database.
|
|
35
|
+
- Clinical Decision Support (CDSS).
|
|
36
|
+
- Laboratory Results delivery.
|
|
37
|
+
- Radiology (PACS) access in the Operating Room.
|
|
38
|
+
|
|
39
|
+
*Recommendation:* Use active-active clustering and tiered Disaster Recovery (RTO < 15 min for critical systems).
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
*Reference for it-manager-hospital HIS/PEP domain expertise.*
|
|
@@ -0,0 +1,52 @@
|
|
|
1
|
+
# Hospital Digital Maturity & Professional Certification
|
|
2
|
+
|
|
3
|
+
A comprehensive guide for the evolution of technological and clinical processes in healthcare.
|
|
4
|
+
|
|
5
|
+
## 1. Accreditation Standards
|
|
6
|
+
|
|
7
|
+
### ONA (Organização Nacional de Acreditação) - Brazil
|
|
8
|
+
- **Nível 1 (Acreditado):** Focus on Patient Safety. Basic structure and safe processes.
|
|
9
|
+
- **Nível 2 (Acreditado Pleno):** Focus on Management. Process integration and departmental alignment.
|
|
10
|
+
- **Nível 3 (Acreditado com Excelência):** Focus on Excellence. Continuous improvement, management maturity, and cycles of outcomes.
|
|
11
|
+
|
|
12
|
+
### HIMSS (Healthcare Information and Management Systems Society)
|
|
13
|
+
- **EMRAM (Electronic Medical Record Adoption Model):** Stages 0 to 7.
|
|
14
|
+
- **Stage 6:** Full Clinical Decision Support (CDSS), closed-loop medication, and paperless nursing.
|
|
15
|
+
- **Stage 7:** Full Interoperability, Advanced Data Analytics (AI), and zero dependency on paper documents.
|
|
16
|
+
|
|
17
|
+
### JCI (Joint Commission International)
|
|
18
|
+
- Rigorous global standards for patient safety, facility management, and high-quality clinical care.
|
|
19
|
+
|
|
20
|
+
## 2. Professional Certification Roadmap (IT in Health)
|
|
21
|
+
|
|
22
|
+
| Credential | Level | Focus | Provider |
|
|
23
|
+
|---|---|---|---|
|
|
24
|
+
| **CAHIMS** | Associate | Entry-level health IT knowledge. | HIMSS |
|
|
25
|
+
| **CPHIMS** | Professional | 5+ years experience IT + 3 years health. | HIMSS |
|
|
26
|
+
| **CHCIO** | Executive | CIO level leadership and strategic vision. | CHIME |
|
|
27
|
+
| **cpTICS** | Specialist | Brazilian standards, LGPD, and PEP. | SBIS |
|
|
28
|
+
|
|
29
|
+
## 3. SBIS cpTICS Study Guide (Brazil)
|
|
30
|
+
|
|
31
|
+
To prepare for the cpTICS exam and lead a digital transformation in Brazil, the following bibliography is essential:
|
|
32
|
+
|
|
33
|
+
### Core Legislation & Strategy
|
|
34
|
+
- **Law 13.709/2018 (LGPD):** Management of sensitive healthcare data.
|
|
35
|
+
- **Law 13.787/2018:** Digitalization and preservation of Electronic Health Records.
|
|
36
|
+
- **Decreto 12.560/2025:** RNDS (Rede Nacional de Dados em Saúde) and SUS Digital Platforms.
|
|
37
|
+
- **Resolução CFM 2.314/2022:** Normative framework for Telemedicine.
|
|
38
|
+
- **Estratégia de Saúde Digital para o Brasil (2020-2028).**
|
|
39
|
+
|
|
40
|
+
### Recommended Bibliography (SBIS)
|
|
41
|
+
- **Coleção de livros de Saúde Digital:** Fundamentals of informatics in health.
|
|
42
|
+
- **Modelo de Informação - Registro de Atendimento Clínico (RAC):** Standards for clinical data capture.
|
|
43
|
+
- **Portaria 701/2022:** Standard informational model for "Sumário de Alta" (Discharge Summary).
|
|
44
|
+
- **PBIA (Plano Brasileiro de Inteligência Artificial):** Future roadmap for clinical AI in Brazil.
|
|
45
|
+
|
|
46
|
+
### Key Courses for Preparation
|
|
47
|
+
- **UNA-SUS:** Digital Health Strategy.
|
|
48
|
+
- **Fiocruz:** Introduction to Digital Health.
|
|
49
|
+
- **ESR (RNP):** LGPD, Telehealth, and digital transition.
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
*Reference for it-manager-hospital certification and maturity advisory.*
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
# IT Manager Pro (Elite Advisor)
|
|
2
|
+
|
|
3
|
+
The ultimate digital leadership companion for IT Managers, CTOs, and Product Leaders.
|
|
4
|
+
|
|
5
|
+
## 🚀 Overview
|
|
6
|
+
|
|
7
|
+
**IT Manager Pro** is a high-fidelity advisory skill designed for the 2026 digital landscape. It provides a multi-expert perspective on the most critical pillars of modern technology leadership:
|
|
8
|
+
- **Strategic Alignment:** Business-IT integration using ITIL 5 (DPSM).
|
|
9
|
+
- **Modern FinOps:** Managing the total value of technology, from cloud to AI inference.
|
|
10
|
+
- **Human Leadership:** Emotional intelligence and performance in VUCA environments.
|
|
11
|
+
- **Data-Driven Governance:** Algorithmic ethics, sustainability (ESG), and continuous improvement.
|
|
12
|
+
|
|
13
|
+
## 👥 The 7-Expert Bench
|
|
14
|
+
|
|
15
|
+
Consult with a virtual team of experts in a single conversation:
|
|
16
|
+
1. **The Strategist:** Value co-creation & ITIL 5.
|
|
17
|
+
2. **The FinOps Auditor:** Budget & GPU/AI value.
|
|
18
|
+
3. **The People Coach:** Leadership & Culture.
|
|
19
|
+
4. **The Risk Guard:** Security & AI Ethics.
|
|
20
|
+
5. **The ESG Officer:** Sustainability.
|
|
21
|
+
6. **The CI Engineer:** Data-driven optimization.
|
|
22
|
+
7. **The Communication Bridge:** C-level storytelling.
|
|
23
|
+
|
|
24
|
+
## 🛠 Usage
|
|
25
|
+
|
|
26
|
+
Simply use the trigger phrases to activate the skill:
|
|
27
|
+
- `it manager pro: we have an outage, help me draft the executive update.`
|
|
28
|
+
- `ti management: what are the key KPIs for ai-native service delivery?`
|
|
29
|
+
- `finops strategy: how do I self-fund our new agentic ai project?`
|
|
30
|
+
|
|
31
|
+
### 💡 Approval-Based Insights (Feature)
|
|
32
|
+
To keep responses concise and high-value, the skill will provide a core answer first and then **ask** if you want deep insights or real-world applicability examples.
|
|
33
|
+
|
|
34
|
+
## 📂 Structure
|
|
35
|
+
|
|
36
|
+
- `SKILL.md`: The core logic and expert instructions.
|
|
37
|
+
- `references/`: Comprehensive reference on FinOps 2.0 and VUCA leadership.
|
|
38
|
+
- `examples/`: Practical scenarios for crisis management, budgeting, and strategy.
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
*Powered by Antigravity Skills Ecosystem.*
|