opencode-skills-collection 4.0.53 → 4.0.55

package/bundled-skills/objection-preemptor/SKILL.md

@@ -116,6 +116,12 @@ Before finalizing output, the agent asks:
 - [ ] Did I use evidence, not empty reassurance?
 - [ ] Does the output preserve autonomy?
 
+## Example
+
+**User request:**
+
+> Identify the recurring objections blocking this offer and revise the pitch to address them with evidence.
+
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

package/bundled-skills/observability-and-instrumentation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: observability-and-instrumentation
-description: Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened...
+description: "Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works."
 risk: critical
 source: https://github.com/addyosmani/agent-skills/tree/main/skills/observability-and-instrumentation
 source_repo: addyosmani/agent-skills
@@ -88,7 +88,10 @@ logger.warn({
 ```typescript
 // Express: child logger per request, ID propagated downstream
 app.use((req, res, next) => {
-  req.id = req.headers['x-request-id'] ?? crypto.randomUUID();
+  const suppliedId = req.headers['x-request-id'];
+  req.id = typeof suppliedId === 'string' && /^[A-Za-z0-9_-]{1,64}$/.test(suppliedId)
+    ? suppliedId
+    : crypto.randomUUID();
   req.log = logger.child({ requestId: req.id });
   res.setHeader('x-request-id', req.id);
   next();

package/bundled-skills/observability-and-instrumentation/references/observability-checklist.md

@@ -0,0 +1,13 @@
+# Instrumentation acceptance checklist
+
+## Inputs
+
+Write the on-call questions and identify the authorized staging environment.
+
+## Procedure and verification
+
+Check structured event names and bounded correlation identifiers; reject or regenerate malformed external identifiers. Confirm redaction on nested errors and request paths. Verify rate, error and duration metrics with bounded labels; follow a request across service boundaries. Exercise an allowed failure and verify its log, metric and trace. Test alert delivery only to an authorized test destination, then restore any changed thresholds.
+
+## Limitations
+
+Record evidence and untested boundaries before launch. Do not send private data to an external telemetry backend without authorization. Head sampling can discard errors before tail sampling sees them; document that coverage limit.

package/bundled-skills/observability-engineer/SKILL.md

@@ -23,12 +23,12 @@ You are an observability engineer specializing in production-grade monitoring, l
 
 1. Identify critical services, user journeys, and reliability targets.
 2. Define signals, instrumentation, and data retention.
-3. Build dashboards and alerts aligned to SLOs.
-4. Validate signal quality and reduce alert noise.
+3. Build the smallest dashboards and actionable alerts needed for those SLOs; define owner, runbook and missing-data behavior.
+4. Reconcile numerator/denominator and sampling, exercise one alert in an authorized test environment, and measure noise before broad rollout.
 
 ## Safety
 
-- Avoid logging sensitive data or secrets.
+- Use an allowlist of telemetry fields. Do not log credentials, raw prompts, query strings or full bodies by default; inspect actual exported data and retention.
 - Use alerting thresholds that balance coverage and noise.
 
 ## Purpose
@@ -45,7 +45,7 @@ Expert observability engineer specializing in comprehensive monitoring strategie
 - CloudWatch comprehensive AWS service monitoring and cost optimization
 - Nagios and Zabbix for traditional infrastructure monitoring
 - Custom metrics collection with StatsD, Telegraf, and Collectd
-- High-cardinality metrics handling and storage optimization
+- Cardinality budgets: avoid user IDs, request IDs and unbounded URLs in metric labels
 
 ### Distributed Tracing & APM
 - Jaeger distributed tracing deployment and trace analysis
@@ -192,7 +192,7 @@ Expert observability engineer specializing in comprehensive monitoring strategie
 - Balances monitoring coverage with system performance impact
 
 ## Knowledge Base
-- Latest observability developments and tool ecosystem evolution (2024/2025)
+- Installed collector/SDK versions and current primary documentation
 - Modern SRE practices and reliability engineering patterns with Google SRE methodology
 - Enterprise monitoring architectures and scalability considerations for Fortune 500 companies
 - Cloud-native observability patterns and Kubernetes monitoring with service mesh integration
@@ -234,7 +234,15 @@ Expert observability engineer specializing in comprehensive monitoring strategie
 - "Design observability strategy for serverless architecture with AWS Lambda and API Gateway"
 - "Create custom metrics pipeline for business KPIs integrated with technical monitoring"
 
+## Worked example and prerequisites
+
+Input: a checkout API has 100,000 eligible requests in a defined window, with 120 failures, and an agreed 99.9% success SLO. Observed success is 99.88%; the 0.12% error ratio consumes budget at 1.2 times the permitted 0.1% ratio for that window. Record which requests count, how retries are handled and whether failures are measured at the user or server boundary.
+
+Before adding an alert, verify that both counters cover the same population, test no-traffic and missing-series behavior, and attach a runbook and owner. Expected: an operator can identify the affected journey and next check without exposing request contents. This arithmetic example is not a prescribed paging threshold or a claim about a live service.
+
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Missing telemetry is unknown health, not automatically zero errors.
+- Sampled traces cannot directly supply an unbiased total request/error denominator without a justified estimator.
+- A dashboard or vendor integration does not establish compliance; access, retention and actual exported payloads still need review.
+- Alert delivery, production instrumentation, chaos experiments and incident messages require authorization for the specific environment and action.

package/bundled-skills/obsidian-bases/SKILL.md

@@ -8,292 +8,15 @@ date_added: "2026-03-21"
 
 # Obsidian Bases Skill
 
+## Detailed Guide
+
+Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
+
 ## When to Use
 - Use when creating or editing `.base` files in Obsidian.
 - Use for database-like note views with filters, formulas, summaries, or cards/tables.
 - Use when the user asks about Obsidian Bases specifically.
 
-## Workflow
-
-1. **Create the file**: Create a `.base` file in the vault with valid YAML content
-2. **Define scope**: Add `filters` to select which notes appear (by tag, folder, property, or date)
-3. **Add formulas** (optional): Define computed properties in the `formulas` section
-4. **Configure views**: Add one or more views (`table`, `cards`, `list`, or `map`) with `order` specifying which properties to display
-5. **Validate**: Verify the file is valid YAML with no syntax errors. Check that all referenced properties and formulas exist. Common issues: unquoted strings containing special YAML characters, mismatched quotes in formula expressions, referencing `formula.X` without defining `X` in `formulas`
-6. **Test in Obsidian**: Open the `.base` file in Obsidian to confirm the view renders correctly. If it shows a YAML error, check quoting rules below
-
-## Schema
-
-Base files use the `.base` extension and contain valid YAML.
-
-```yaml
-# Global filters apply to ALL views in the base
-filters:
-  # Can be a single filter string
-  # OR a recursive filter object with and/or/not
-  and: []
-  or: []
-  not: []
-
-# Define formula properties that can be used across all views
-formulas:
-  formula_name: 'expression'
-
-# Configure display names and settings for properties
-properties:
-  property_name:
-    displayName: "Display Name"
-  formula.formula_name:
-    displayName: "Formula Display Name"
-  file.ext:
-    displayName: "Extension"
-
-# Define custom summary formulas
-summaries:
-  custom_summary_name: 'values.mean().round(3)'
-
-# Define one or more views
-views:
-  - type: table | cards | list | map
-    name: "View Name"
-    limit: 10                    # Optional: limit results
-    groupBy:                     # Optional: group results
-      property: property_name
-      direction: ASC | DESC
-    filters:                     # View-specific filters
-      and: []
-    order:                       # Properties to display in order
-      - file.name
-      - property_name
-      - formula.formula_name
-    summaries:                   # Map properties to summary formulas
-      property_name: Average
-```
-
-## Filter Syntax
-
-Filters narrow down results. They can be applied globally or per-view.
-
-### Filter Structure
-
-```yaml
-# Single filter
-filters: 'status == "done"'
-
-# AND - all conditions must be true
-filters:
-  and:
-    - 'status == "done"'
-    - 'priority > 3'
-
-# OR - any condition can be true
-filters:
-  or:
-    - 'file.hasTag("book")'
-    - 'file.hasTag("article")'
-
-# NOT - exclude matching items
-filters:
-  not:
-    - 'file.hasTag("archived")'
-
-# Nested filters
-filters:
-  or:
-    - file.hasTag("tag")
-    - and:
-        - file.hasTag("book")
-        - file.hasLink("Textbook")
-    - not:
-        - file.hasTag("book")
-        - file.inFolder("Required Reading")
-```
-
-### Filter Operators
-
-| Operator | Description |
-|----------|-------------|
-| `==` | equals |
-| `!=` | not equal |
-| `>` | greater than |
-| `<` | less than |
-| `>=` | greater than or equal |
-| `<=` | less than or equal |
-| `&&` | logical and |
-| `\|\|` | logical or |
-| <code>!</code> | logical not |
-
-## Properties
-
-### Three Types of Properties
-
-1. **Note properties** - From frontmatter: `note.author` or just `author`
-2. **File properties** - File metadata: `file.name`, `file.mtime`, etc.
-3. **Formula properties** - Computed values: `formula.my_formula`
-
-### File Properties Reference
-
-| Property | Type | Description |
-|----------|------|-------------|
-| `file.name` | String | File name |
-| `file.basename` | String | File name without extension |
-| `file.path` | String | Full path to file |
-| `file.folder` | String | Parent folder path |
-| `file.ext` | String | File extension |
-| `file.size` | Number | File size in bytes |
-| `file.ctime` | Date | Created time |
-| `file.mtime` | Date | Modified time |
-| `file.tags` | List | All tags in file |
-| `file.links` | List | Internal links in file |
-| `file.backlinks` | List | Files linking to this file |
-| `file.embeds` | List | Embeds in the note |
-| `file.properties` | Object | All frontmatter properties |
-
-### The `this` Keyword
-
-- In main content area: refers to the base file itself
-- When embedded: refers to the embedding file
-- In sidebar: refers to the active file in main content
-
-## Formula Syntax
-
-Formulas compute values from properties. Defined in the `formulas` section.
-
-```yaml
-formulas:
-  # Simple arithmetic
-  total: "price * quantity"
-
-  # Conditional logic
-  status_icon: 'if(done, "✅", "⏳")'
-
-  # String formatting
-  formatted_price: 'if(price, price.toFixed(2) + " dollars")'
-
-  # Date formatting
-  created: 'file.ctime.format("YYYY-MM-DD")'
-
-  # Calculate days since created (use .days for Duration)
-  days_old: '(now() - file.ctime).days'
-
-  # Calculate days until due date
-  days_until_due: 'if(due_date, (date(due_date) - today()).days, "")'
-```
-
-## Key Functions
-
-Most commonly used functions. For the complete reference of all types (Date, String, Number, List, File, Link, Object, RegExp), see [FUNCTIONS_REFERENCE.md](references/FUNCTIONS_REFERENCE.md).
-
-| Function | Signature | Description |
-|----------|-----------|-------------|
-| `date()` | `date(string): date` | Parse string to date (`YYYY-MM-DD HH:mm:ss`) |
-| `now()` | `now(): date` | Current date and time |
-| `today()` | `today(): date` | Current date (time = 00:00:00) |
-| `if()` | `if(condition, trueResult, falseResult?)` | Conditional |
-| `duration()` | `duration(string): duration` | Parse duration string |
-| `file()` | `file(path): file` | Get file object |
-| `link()` | `link(path, display?): Link` | Create a link |
-
-### Duration Type
-
-When subtracting two dates, the result is a **Duration** type (not a number).
-
-**Duration Fields:** `duration.days`, `duration.hours`, `duration.minutes`, `duration.seconds`, `duration.milliseconds`
-
-**IMPORTANT:** Duration does NOT support `.round()`, `.floor()`, `.ceil()` directly. Access a numeric field first (like `.days`), then apply number functions.
-
-```yaml
-# CORRECT: Calculate days between dates
-"(date(due_date) - today()).days"                    # Returns number of days
-"(now() - file.ctime).days"                          # Days since created
-"(date(due_date) - today()).days.round(0)"           # Rounded days
-
-# WRONG - will cause error:
-# "((date(due) - today()) / 86400000).round(0)"      # Duration doesn't support division then round
-```
-
-### Date Arithmetic
-
-```yaml
-# Duration units: y/year/years, M/month/months, d/day/days,
-#                 w/week/weeks, h/hour/hours, m/minute/minutes, s/second/seconds
-"now() + \"1 day\""       # Tomorrow
-"today() + \"7d\""        # A week from today
-"now() - file.ctime"      # Returns Duration
-"(now() - file.ctime).days"  # Get days as number
-```
-
-## View Types
-
-### Table View
-
-```yaml
-views:
-  - type: table
-    name: "My Table"
-    order:
-      - file.name
-      - status
-      - due_date
-    summaries:
-      price: Sum
-      count: Average
-```
-
-### Cards View
-
-```yaml
-views:
-  - type: cards
-    name: "Gallery"
-    order:
-      - file.name
-      - cover_image
-      - description
-```
-
-### List View
-
-```yaml
-views:
-  - type: list
-    name: "Simple List"
-    order:
-      - file.name
-      - status
-```
-
-### Map View
-
-Requires latitude/longitude properties and the Maps community plugin.
-
-```yaml
-views:
-  - type: map
-    name: "Locations"
-    # Map-specific settings for lat/lng properties
-```
-
-## Default Summary Formulas
-
-| Name | Input Type | Description |
-|------|------------|-------------|
-| `Average` | Number | Mathematical mean |
-| `Min` | Number | Smallest number |
-| `Max` | Number | Largest number |
-| `Sum` | Number | Sum of all numbers |
-| `Range` | Number | Max - Min |
-| `Median` | Number | Mathematical median |
-| `Stddev` | Number | Standard deviation |
-| `Earliest` | Date | Earliest date |
-| `Latest` | Date | Latest date |
-| `Range` | Date | Latest - Earliest |
-| `Checked` | Boolean | Count of true values |
-| `Unchecked` | Boolean | Count of false values |
-| `Empty` | Any | Count of empty values |
-| `Filled` | Any | Count of non-empty values |
-| `Unique` | Any | Count of unique values |
-
 ## Complete Examples
 
 ### Task Tracker Base
@@ -419,91 +142,6 @@ views:
       - file.mtime
 ```
 
-## Embedding Bases
-
-Embed in Markdown files:
-
-```markdown
-![[MyBase.base]]
-
-<!-- Specific view -->
-![[MyBase.base#View Name]]
-```
-
-## YAML Quoting Rules
-
-- Use single quotes for formulas containing double quotes: `'if(done, "Yes", "No")'`
-- Use double quotes for simple strings: `"My View Name"`
-- Escape nested quotes properly in complex expressions
-
-## Troubleshooting
-
-### YAML Syntax Errors
-
-**Unquoted special characters**: Strings containing `:`, `{`, `}`, `[`, `]`, `,`, `&`, `*`, `#`, `?`, `|`, `-`, `<`, `>`, `=`, `!`, `%`, `@`, `` ` `` must be quoted.
-
-```yaml
-# WRONG - colon in unquoted string
-displayName: Status: Active
-
-# CORRECT
-displayName: "Status: Active"
-```
-
-**Mismatched quotes in formulas**: When a formula contains double quotes, wrap the entire formula in single quotes.
-
-```yaml
-# WRONG - double quotes inside double quotes
-formulas:
-  label: "if(done, "Yes", "No")"
-
-# CORRECT - single quotes wrapping double quotes
-formulas:
-  label: 'if(done, "Yes", "No")'
-```
-
-### Common Formula Errors
-
-**Duration math without field access**: Subtracting dates returns a Duration, not a number. Always access `.days`, `.hours`, etc.
-
-```yaml
-# WRONG - Duration is not a number
-"(now() - file.ctime).round(0)"
-
-# CORRECT - access .days first, then round
-"(now() - file.ctime).days.round(0)"
-```
-
-**Missing null checks**: Properties may not exist on all notes. Use `if()` to guard.
-
-```yaml
-# WRONG - crashes if due_date is empty
-"(date(due_date) - today()).days"
-
-# CORRECT - guard with if()
-'if(due_date, (date(due_date) - today()).days, "")'
-```
-
-**Referencing undefined formulas**: Ensure every `formula.X` in `order` or `properties` has a matching entry in `formulas`.
-
-```yaml
-# This will fail silently if 'total' is not defined in formulas
-order:
-  - formula.total
-
-# Fix: define it
-formulas:
-  total: "price * quantity"
-```
-
-## References
-
-- [Bases Syntax](https://help.obsidian.md/bases/syntax)
-- [Functions](https://help.obsidian.md/bases/functions)
-- [Views](https://help.obsidian.md/bases/views)
-- [Formulas](https://help.obsidian.md/formulas)
-- [Complete Functions Reference](references/FUNCTIONS_REFERENCE.md)
-
 ## Limitations
 - Use this skill only when the task clearly matches the scope described above.
 - Do not treat the output as a substitute for environment-specific validation, testing, or expert review.