opencode-skills-collection 4.1.1 → 4.1.3

package/bundled-skills/git-commit-message/SKILL.md

@@ -0,0 +1,76 @@
+---
+name: git-commit-message
+description: "Generates conventional-commit messages from staged changes: type prefix + English imperative subject (≤50 chars) + optional body explaining why. Use when the user asks to write, generate, or polish a git commit message."
+category: development
+risk: safe
+source: https://github.com/alapha888/agent-skills-en
+source_repo: alapha888/agent-skills-en
+source_type: community
+date_added: "2026-10-01"
+author: alapha888
+tags: [git, commit-messages, conventional-commits]
+tools: [claude, cursor, gemini, codex]
+license: MIT
+license_source: https://github.com/alapha888/agent-skills-en/blob/main/LICENSE
+---
+
+# Git Commit Message Generation
+
+Generate a commit message from the actual staged changes (`git diff --cached`). The message must let a reader know "what changed and why" without opening the diff.
+
+## When to Use
+
+- Use when the user asks to write, generate, or polish a git commit message.
+- Use when staged changes need a conventional-commit message with a why-focused body.
+
+## Workflow
+
+1. **Look at the changes**: run `git status --short` and `git diff --cached --stat` to confirm there is something staged. If the staging area is empty, stop and ask the user — never invent a commit message out of nothing.
+2. **Pick a type**: choose exactly one type prefix based on the changes (if one commit mixes types, ask the user to split it):
+   - `feat`: new feature
+   - `fix`: bug fix
+   - `docs`: documentation only
+   - `refactor`: refactor (behavior unchanged)
+   - `test`: add or change tests
+   - `chore`: build, dependencies, misc
+3. **Write the subject**: format `type: English imperative phrase`, ≤50 characters. Start with a verb: "Add…", "Fix…", "Remove…", "Unify…". Ban empty subjects like "update code", "some changes", "fix bug".
+4. **Write the body (optional but recommended)**: 1–3 lines explaining *why*, not a play-by-play of *how*. Bug fixes must state the trigger conditions; features should describe the user-visible change.
+5. **Output**: give a ready-to-run command, not bare text the user has to assemble.
+
+## Rules
+
+- The subject is for skimmers; the body is for future-you in three months. Keep the two jobs separate.
+- A change mixing a feature and a refactor should become two commits, not one `feat` that papers over the mess.
+- No meta-commentary in the message ("generated by AI", etc.) — the message is about the change, nothing else.
+
+## Minimal example (runnable)
+
+```bash
+# 1. Look at the changes first
+git status --short
+git diff --cached --stat
+
+# 2. Suppose the change: added CAPTCHA verification to the login endpoint
+# Generated commit:
+git commit -m "feat: add CAPTCHA verification to login endpoint" -m "Blocks automated credential stuffing; CAPTCHA valid 5 minutes, account locks 10 minutes after 3 failures."
+```
+
+Another example (bug fixes must state trigger conditions):
+
+```bash
+git commit -m "fix: keep order-list filters across pagination" -m "Trigger: filter first, then turn the page. Cause: page turns dropped the query params."
+```
+
+## Limitations
+
+- Only writes the message. Staging, splitting, committing and pushing remain the user's decision, and the skill never runs `git commit` on its own.
+- The 50-character subject and imperative-mood conventions are the common default; repositories with their own commit convention (Gitmoji, Jira prefixes, project overrides) take precedence over this skill.
+- It reads the staged diff, so it cannot describe intent that the diff alone does not show. When the "why" is not inferable, the skill asks instead of inventing it.
+- Generated or vendored changes (lockfiles, minified output) are summarized collectively rather than listed line by line.
+
+## Anti-patterns
+
+- ❌ Writing a message for an empty staging area: no `git diff --cached`, no commit message.
+- ❌ Catch-all `chore`: labeling every feat and fix as `chore` until the type system means nothing.
+- ❌ Novel-length subjects: `feat: add a really useful feature that greatly improves the user experience` — the subject says *what*, leave praise to the user.
+- ❌ Body as implementation log: "first changed line 20 of a.py, then b.py…" — the diff already shows that; the body explains why.

package/bundled-skills/health-wellness/SKILL.md

@@ -0,0 +1,334 @@
+---
+name: health-wellness
+description: 'Wellbeing check-in register: anonymous flag, department, check-in date, wellbeing score, stress and energy levels, support and resource flags, confidentiality and status. Use for wellness programmes.'
+category: business
+risk: safe
+source: self
+source_type: self
+date_added: "2026-09-26"
+author: WHOISABHISHEKADHIKARI
+tags: [sme, business, operations, database, csv, notion, sql, engage]
+tools: []
+source_repo: WHOISABHISHEKADHIKARI/sme-ops-system-builder
+---
+
+# Health & Wellness
+
+**What it is:** Wellbeing tracking.
+
+## Overview
+
+Works out the smallest useful **Health & Wellness** setup for the business in front of it, then
+builds it only when asked. The default output is a short recommendation, not a
+spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on
+request, from one field list so they cannot drift apart.
+
+Layer: Layer 6: Engage. Fits: Scale stage. Table code: n/a.
+
+## When to Use This Skill
+
+- employee wellbeing
+- health check in tracker
+- wellness survey
+- mental health support log
+
+Also use it when the user says "wellbeing tracking", or describes the same process happening in a
+spreadsheet, a document or someone inboxes.
+
+Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces
+empty templates only - it never holds or processes real employee or customer data.
+
+## How It Works
+
+Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.
+
+### Step 1 - Identify intent
+
+Read the request and pick the intent before asking anything.
+
+- "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
+- "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
+- "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
+- "how do I ..." -> advice question; answer directly and offer the build only if it helps.
+
+Ask only if this is the highest-value missing fact; otherwise proceed without an opener:
+
+> **Q:** Is this for employees or a team?
+
+### Step 2 - Ask only what is missing
+
+Skip anything the user already answered, in any earlier message. Ask the rest one at a
+time, and stop as soon as the remaining answers would not change the output.
+
+- **Scope** - Who is it for? / How many people? / Perks or programmes?
+- **Use** - What is offered? / Optional or mandatory? / Any medical data?
+- **Privacy** - Is it anonymous? / Who can see participation? / Any health details held?
+- **Current process** - Anything offered now? / How is it communicated? / Is uptake tracked?
+- **Outcome** - What do you need? / A benefits list, participation counts or both?
+
+Never invent an answer. If the user does not know, record it as unknown and carry on.
+
+### Step 3 - Hold the internal context
+
+Hold the answers in this shape. It stays internal - it is not shown to the user unless
+they ask, and it never carries a value the user did not give.
+
+```yaml
+module: health-wellness
+intent: null            # setup | advice | review | fix | build | convert | export
+scale: null             # Starter | Growth | Scale, only if the answer changes it
+areas:
+  "Scope": null
+  "Use": null
+  "Privacy": null
+  "Current process": null
+  "Outcome": null
+requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
+confirmed_facts: []     # only what the user actually said
+open_questions: []      # the unanswered ones, in the order worth asking
+```
+
+### Step 4 - Recommend the smallest workflow
+
+If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.
+
+**Recommended approach:** Track benefits and uptake only. Do not store any individual health information, since the benefit does not need it.
+
+**Why this one:** Wellness programmes create risk the moment individual health data is held. Keep participation counts and leave the details out.
+
+**Workflow:** Benefit offered → Uptake count → Anonymous feedback → Review
+
+### Step 5 - Build only on request
+
+Once the user asks for it, derive the fields from the confirmed context and emit the
+requested artifacts. For machine-readable text, keep prose outside the data; for files,
+provide a usable link. Report material validation failures or limitations separately.
+
+**A selected Notion output is rendered by `notion-manual-import`, so route the
+Notion step there.** When the user selects Notion, hand that step to
+@notion-manual-import: it holds the CSV, the property
+mapping, the import steps and the verification checklist, and it renders the Field
+Reference below instead of defining a table of its own. Do not restate the mapping
+here and do not improvise the import steps. Manual CSV and mapping outputs need no
+connection. For requested workspace changes, follow the shared contract: verify actual
+tool access and the target before writing. A user saying "connected" is not tool evidence.
+Never ask for a Notion password or token.
+
+For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the
+text correctly. A CSV is not an `.xlsx` workbook; create `.xlsx` only when the user
+requests a workbook.
+A CSV carries no types, so after it, name the columns
+that need a number, date or currency format applied.
+
+```csv
+Check-in Title,Employee Name,Anonymous,Department,Check-in Date,Wellbeing Score,Stress Level,Energy Level,Support Requested,Resource Shared,Confidential,Status,Wellness ID
+Weekly wellbeing check,Aarav Sharma,FALSE,Delivery,2026-01-15,4,Low,Low,FALSE,FALSE,Internal,Completed,
+```
+
+```sql
+CREATE TABLE health_wellness (
+  check_in_title VARCHAR(255),
+  employee_name VARCHAR(255),
+  anonymous BOOLEAN NOT NULL,
+  department VARCHAR(255),
+  check_in_date DATE NOT NULL,
+  wellbeing_score NUMERIC NOT NULL,
+  stress_level VARCHAR(100) NOT NULL,
+  energy_level VARCHAR(100) NOT NULL,
+  support_requested BOOLEAN NOT NULL,
+  resource_shared BOOLEAN NOT NULL,
+  confidential VARCHAR(100) NOT NULL,
+  status VARCHAR(100) NOT NULL,
+  wellness_id SERIAL PRIMARY KEY,
+  created_at TIMESTAMP DEFAULT NOW(),
+  updated_at TIMESTAMP DEFAULT NOW()
+);
+
+CREATE INDEX idx_health_wellness_status ON health_wellness (status);
+```
+
+```json
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Health & Wellness",
+  "type": "object",
+  "additionalProperties": false,
+  "properties": {
+      "Check-in Title": { "type": "string" },
+      "Employee Name": { "type": "string" },
+      "Anonymous": { "type": "boolean" },
+      "Department": { "type": "string" },
+      "Check-in Date": { "type": "string", "format": "date" },
+      "Wellbeing Score": { "type": "number" },
+      "Stress Level": { "type": "string" },
+      "Energy Level": { "type": "string" },
+      "Support Requested": { "type": "boolean" },
+      "Resource Shared": { "type": "boolean" },
+      "Confidential": { "type": "string" },
+      "Status": { "type": "string" },
+      "Wellness ID": { "type": "integer" }
+  },
+  "required": [
+      "Check-in Date",
+      "Wellbeing Score",
+      "Stress Level",
+      "Energy Level",
+      "Confidential",
+      "Status"
+  ]
+}
+```
+
+```markdown
+| CSV column | Notion property | Set after import |
+|---|---|---|
+| Check-in Title | Title | Use as the database title |
+| Employee Name | Text | Leave as Text |
+| Anonymous | Checkbox | Convert to Checkbox |
+| Department | Text | Leave as Text |
+| Check-in Date | Date | Convert to Date |
+| Wellbeing Score | Number | Convert to Number |
+| Stress Level | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Critical" |
+| Energy Level | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High" |
+| Support Requested | Checkbox | Convert to Checkbox |
+| Resource Shared | Checkbox | Convert to Checkbox |
+| Confidential | Select (add options after import) | Convert to Select, add options: "Public", "Internal", "Restricted", "Highly Restricted" |
+| Status | Select (add options after import) | Convert to Select, add options: "Scheduled", "Completed", "Missed", "Follow-up Due" |
+| Wellness ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |
+```
+
+The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays `currency`, dates stay `date`,
+and anything pointing at another table stays `relation`.
+
+## Field Reference
+
+| # | Field | Type | SQL | JSON Schema | Notion | CSV example |
+|---:|---|---|---|---|---|---|
+| 1 | Check-in Title | `text` | `VARCHAR(255)` | `string` | Text | `Weekly wellbeing check` |
+| 2 | Employee Name | `text` | `VARCHAR(255)` | `string` | Text | `Aarav Sharma` |
+| 3 | Anonymous | `checkbox` | `BOOLEAN` | `boolean` | Checkbox | `FALSE` |
+| 4 | Department | `text` | `VARCHAR(255)` | `string` | Text | `Delivery` |
+| 5 | Check-in Date | `date` | `DATE` | `string, format: date` | Date | `2026-01-15` |
+| 6 | Wellbeing Score | `number` | `NUMERIC` | `number` | Number | `4` |
+| 7 | Stress Level | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Low` |
+| 8 | Energy Level | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Low` |
+| 9 | Support Requested | `checkbox` | `BOOLEAN` | `boolean` | Checkbox | `FALSE` |
+| 10 | Resource Shared | `checkbox` | `BOOLEAN` | `boolean` | Checkbox | `FALSE` |
+| 11 | Confidential | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Internal` |
+| 12 | Status | `select` | `VARCHAR(100)` | `string` | Select (add options after import) | `Completed` |
+| 13 | Wellness ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text (preserve source ID) | `(blank)` |
+
+## Select Options
+
+**Stress Level**
+
+```
+Low | Medium | High | Critical
+```
+**Energy Level**
+
+```
+Low | Medium | High
+```
+**Confidential**
+
+```
+Public | Internal | Restricted | Highly Restricted
+```
+**Status**
+
+```
+Scheduled | Completed | Missed | Follow-up Due
+```
+
+## Relations
+
+Link fields: none
+
+## Examples
+
+**Prompt**
+
+```
+We want a wellness benefit but do not know whether anyone uses it.
+```
+
+**Context first** - one question per message, nothing already answered:
+
+> **Q:** Who is it for?
+> **A:** All employees.
+>
+> **Q:** Do you store health data?
+> **A:** No, and I do not want to.
+>
+> **Q:** What is offered?
+> **A:** A gym allowance and counselling.
+
+**Recommended next step** - offered, not built:
+
+> Track benefits and uptake only. Do not store any individual health information, since the benefit does not need it.
+>
+> Workflow: Benefit offered → Uptake count → Anonymous feedback → Review
+>
+> Want the CSV, SQL, JSON Schema and Notion mapping for this?
+
+## Best Practices
+
+- Build when requested; recommend and offer a build for advice-only requests.
+- One question per message. A batched intake reads as a form and gets guessed at.
+- Keep display names identical across CSV and JSON; document normalized SQL identifiers.
+- Use `relation` for anything that points at another table, `text` only for free text.
+- Money fields are `currency`, never `text`. Dates are `date`, never free text.
+- If the user requests an example row, keep it obviously fake so nobody imports it as real data.
+
+## Limitations
+
+- Empty template only. It does not compute payroll, tax, leave balances or KPIs.
+- Notion relations need both databases imported before the link column resolves.
+- Select options are a starting set. Rename them to match how the business talks.
+- No automation, reminders or sync. Those need the integration layer.
+- Does not provide medical advice, cover or any health service.
+- Legal, tax and HR review is still required before this drives real decisions.
+
+## Security & Safety Notes
+
+- Never fill in real names, salaries, medical or banking data. Placeholders only.
+- Label example rows as synthetic, and keep bank details masked.
+- Local reads, generation commands, and validation are part of a requested artifact build.
+  External writes, messages, provisioning, and publication require authorization for that
+  action and target; existing explicit authorization does not need to be repeated.
+- If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what
+  the requested review needs; keep generated templates empty. Do not claim deletion
+  from the conversation or service storage.
+- Privacy, legal and disciplinary cases need a qualified human reviewer before anything
+  is acted on.
+
+## Common Pitfalls
+
+- **Problem:** a static mapping is described as a completed workspace build.
+  **Solution:** deliver manual mappings without a connection; claim a live change only
+  after the authorized tool operation succeeds.
+- **Problem:** asked all six questions in one message.
+  **Solution:** ask one, wait, and drop any the first answer already covered.
+- **Problem:** built a full system when one table was asked for.
+  **Solution:** build what was requested; mention the parent skill separately.
+- **Problem:** all four artifacts drift apart.
+  **Solution:** derive all four from the field list in this file, never by hand.
+- **Problem:** Notion import shows every column as Text.
+  **Solution:** that is expected. Apply the property mapping table once, after import.
+
+## Related Skills
+
+- ](https://github.com/sickn33/agentic-awesome-skills/blob/main/CATALOG.md) - find the relevant module, then read its skill.
+- @people-directory - the employee master record most modules link to.
+- @notification-reminder-hub - turns due dates in this module into reminders.
+
+## Reusable Prompt
+
+```
+I want to set up wellbeing tracking for my company.
+Ask me one short question at a time, and only about what I have not already told you.
+Then recommend the smallest setup that fits, and wait for me to ask before you build it.
+When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.
+```
+

package/bundled-skills/idea-to-blueprint/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mahdi
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.