opencode-skills-collection 4.1.2 → 4.1.4

package/bundled-skills/stellar-multisig-threshold-coordinator/SKILL.md

@@ -0,0 +1,112 @@
+---
+name: stellar-multisig-threshold-coordinator
+description: 'Multi-signature signer and threshold coordination register: weight configurations, master key locks, and cosigner quorum thresholds for Stellar.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, multisig, security, governance, web3, auth]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Stellar Multi-Sig Threshold Coordinator
+
+**What it is:** Maintains cryptographic signer weights, transaction authorization thresholds, and master key security boundaries for multi-signature accounts on Stellar.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Stellar Multi-Sig Threshold Coordinator** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Stellar Multi-Sig Threshold Coordinator.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Coordination Record ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `MSIG-001` |
+| 2 | Controlled Account ID | `text` | `VARCHAR(56)` | `string` | Text | `GCTRL...` |
+| 3 | Low Threshold Weight | `number` | `INTEGER` | `number` | Number | `1` |
+| 4 | Medium Threshold Weight | `number` | `INTEGER` | `number` | Number | `2` |
+| 5 | High Threshold Weight | `number` | `INTEGER` | `number` | Number | `3` |
+| 6 | Master Key Weight | `number` | `INTEGER` | `number` | Number | `0` |
+| 7 | Active Signers Count | `number` | `INTEGER` | `number` | Number | `4` |
+| 8 | Signer Weight Sum | `number` | `INTEGER` | `number` | Number | `4` |
+| 9 | Quorum Configuration State | `select` | `VARCHAR(32)` | `string` | Select | `Secured` |
+| 10 | Emergency Override Signer | `text` | `VARCHAR(56)` | `string` | Text | `GEMERG...` |
+| 11 | Threshold Audit Timestamp | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Quorum Configuration State**
+
+```
+Draft Pending | Secured | Sub-Quorum Warning | Degraded Key
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Stellar Multi-Sig Threshold Coordinator for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @stellar-anchor-integration - covers SEP-10 and SEP-24 anchor compliance flows.
+- @stellar-escrow-timelock - covers conditional escrow and timelock settlement.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Stellar Multi-Sig Threshold Coordinator register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/tech-writing-proofread/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: tech-writing-proofread
+description: "Proofreads English technical writing for typos, grammar, punctuation, terminology consistency, jargon, and structure; returns an itemized Original → Suggestion → Reason list without rewriting the document. Use when asked to proofread or polish a technical doc, README, or blog draft."
+category: writing
+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: [proofreading, technical-writing, editing]
+tools: [claude, cursor, gemini, codex]
+license: MIT
+license_source: https://github.com/alapha888/agent-skills-en/blob/main/LICENSE
+---
+
+# Technical Writing Proofreading
+
+Take an English technical document from "understandable" to "publishable." Proofread only — never rewrite content. Flag suspected factual errors; do not silently fix them.
+
+## When to Use
+
+- Use when the user asks to proofread, polish, or review an English technical doc, README, or blog draft.
+- Use when terminology consistency or jargon needs checking across a document.
+
+## Workflow
+
+1. **Read for tone first**: Read the whole document and identify its type (tutorial / API reference / blog post / README). Tutorials tolerate a conversational voice; API references must be precise.
+2. **Build a terminology list**: Scan for key terms (e.g. "callback" vs "callback function", "sign in" vs "log in") and check whether one concept is named several ways. Standardize on the most frequent form and note it in the checklist.
+3. **Check paragraph by paragraph**, but only for these six categories — do not drift into "is this paragraph well written":
+   - Typos and spelling: transposed letters, doubled words ("the the"), commonly confused pairs ("affect/effect", "its/it's", "complement/compliment").
+   - Grammar: subject-verb agreement, verb tense consistency within a procedure, dangling modifiers, missing articles before singular countable nouns.
+   - Punctuation: consistent serial (Oxford) comma usage; hyphens in compound adjectives ("command-line tool"); no double spaces after periods; consistent use of em dashes vs parentheses.
+   - Inline code and proper nouns: inline code, commands, file names, and paths in backticks; proper nouns in their official casing (`GitHub`, not `github`; `JavaScript`, not `Javascript`).
+   - Sentence style: prefer active voice ("The system calls the function" over "The function is called by the system"); cut filler ("basically", "simply", "just", "very"); one idea per sentence.
+   - Structure: headings in parallel form; lists use parallel items; steps in a procedure are imperative and numbered; acronyms are expanded on first use.
+4. **Output the checklist**: list items as "Original → Suggestion → Reason", with line numbers or short quotes. Mark uncertain items `[verify]` instead of forcing a change.
+5. **Close with statistics**: N items total, of which typos x, grammar y, terminology z, style w — so the author sees the distribution at a glance.
+
+## Rules
+
+- Fix language, not facts. A suspected factual error becomes `[verify] This contradicts the usual definition — please confirm`, never a silent "correction."
+- Do not rewrite whole paragraphs. Even a wordy paragraph gets only specific, fixable sentences flagged; keep the author's voice.
+- One pass only. Do not keep "polishing another round" — the deliverable is a "no-defects" checklist, not a perfect text.
+
+## Minimal example
+
+Input snippet:
+
+```text
+This function will be called by the system after the data is ready, you can use it to basically handle the registration of the callback, the timeout is 5 s, examples on github can be referenced.
+```
+
+Output checklist:
+
+```text
+1. [Style] "will be called by the system" → "the system calls" (passive → active)
+2. [Style] "basically handle" → "handle" (cut filler word)
+3. [Terminology] "callback" — if written elsewhere as "callback function", unify on one form (most frequent wins)
+4. [Grammar] run-on sentence: split after "ready." into two sentences
+5. [Proper noun] "github" → "GitHub" (official casing)
+
+Statistics: 5 items — style 2, terminology 1, grammar 1, proper noun 1.
+```
+
+## Limitations
+
+- Proofreads; it does not rewrite. Voice, structure and argument are preserved, so a document that is poorly argued stays poorly argued after review.
+- The technical claims themselves are out of scope: an uncertain statement is left intact rather than silently "corrected" into a different fact.
+- Terminology consistency is judged against the document's own dominant usage, not against an external glossary unless the user supplies one.
+- Only English proofreading is claimed. Other languages, translation quality and localisation review are outside this skill.
+
+## Anti-patterns
+
+- ❌ Turning proofreading into rewriting: tearing a paragraph down so the author's voice and structure are lost.
+- ❌ Hallucinated "corrections": changing an uncertain technical statement as if it were a typo, introducing a factual error.
+- ❌ Typos-only checks: inconsistent terminology and sloppy structure are the real defects in technical docs.
+- ❌ Endless iteration: the user says "polish it once more" and it never ends — the deliverable is the checklist, not a perfect text.

package/bundled-skills/typescript-expert/scripts/ts_diagnostic.py

@@ -10,21 +10,42 @@ import os
 import json
 from pathlib import Path
 
-def run_cmd(cmd: str) -> str:
-    """Run shell command and return output."""
+def run_cmd(args):
+    """Run a command as an argument list (no shell) and return its output."""
     try:
-        result = subprocess.run(cmd, shell=True, capture_output=True, text=True)
+        result = subprocess.run(args, capture_output=True, text=True)
         return result.stdout + result.stderr
     except Exception as e:
         return str(e)
 
+def grep_source_count(pattern: str, exclude: str | None = None) -> tuple[int, list[str]]:
+    """Count and sample lines containing ``pattern`` under ``src/``.
+
+    Pure-Python replacement for ``grep -r ... src/`` so no shell is involved.
+    """
+    root = Path("src")
+    if not root.is_dir():
+        return 0, []
+    matches: list[str] = []
+    for path in sorted(root.rglob("*")):
+        if path.suffix not in (".ts", ".tsx") or not path.is_file():
+            continue
+        try:
+            text = path.read_text(encoding="utf-8", errors="replace")
+        except OSError:
+            continue
+        for lineno, line in enumerate(text.splitlines(), start=1):
+            if pattern in line and (exclude is None or exclude not in line):
+                matches.append(f"{path}:{lineno}:{line}")
+    return len(matches), matches
+
 def check_versions():
     """Check TypeScript and Node versions."""
     print("\n📦 Versions:")
     print("-" * 40)
     
-    ts_version = run_cmd("npx tsc --version 2>/dev/null").strip()
-    node_version = run_cmd("node -v 2>/dev/null").strip()
+    ts_version = run_cmd(["npx", "tsc", "--version"]).strip()
+    node_version = run_cmd(["node", "-v"]).strip()
     
     print(f"  TypeScript: {ts_version or 'Not found'}")
     print(f"  Node.js: {node_version or 'Not found'}")
@@ -134,11 +155,12 @@ def check_type_errors():
     print("\n🔍 Type Check:")
     print("-" * 40)
     
-    result = run_cmd("npx tsc --noEmit 2>&1 | head -20")
+    result = run_cmd(["npx", "tsc", "--noEmit"])
+    lines = result.splitlines()
     if "error TS" in result:
         errors = result.count("error TS")
         print(f"  ❌ {errors}+ type errors found")
-        print(result[:500])
+        print("\n".join(lines[:20])[:500])
     else:
         print("  ✅ No type errors")
 
@@ -147,13 +169,11 @@ def check_any_usage():
     print("\n⚠️ 'any' Type Usage:")
     print("-" * 40)
     
-    result = run_cmd("grep -r ': any' --include='*.ts' --include='*.tsx' src/ 2>/dev/null | wc -l")
-    count = result.strip()
-    if count and count != "0":
+    count, matches = grep_source_count(": any")
+    if count:
         print(f"  ⚠️ Found {count} occurrences of ': any'")
-        sample = run_cmd("grep -rn ': any' --include='*.ts' --include='*.tsx' src/ 2>/dev/null | head -5")
-        if sample:
-            print(sample)
+        if matches:
+            print("\n".join(matches[:5]))
     else:
         print("  ✅ No explicit 'any' types found")
 
@@ -162,9 +182,8 @@ def check_type_assertions():
     print("\n⚠️ Type Assertions (as):")
     print("-" * 40)
     
-    result = run_cmd("grep -r ' as ' --include='*.ts' --include='*.tsx' src/ 2>/dev/null | grep -v 'import' | wc -l")
-    count = result.strip()
-    if count and count != "0":
+    count, _ = grep_source_count(" as ", exclude="import")
+    if count:
         print(f"  ⚠️ Found {count} type assertions")
     else:
         print("  ✅ No type assertions found")
@@ -174,9 +193,11 @@ def check_performance():
     print("\n⏱️ Type Check Performance:")
     print("-" * 40)
     
-    result = run_cmd("npx tsc --extendedDiagnostics --noEmit 2>&1 | grep -E 'Check time|Files:|Lines:|Nodes:'")
-    if result.strip():
-        for line in result.strip().split('\n'):
+    result = run_cmd(["npx", "tsc", "--extendedDiagnostics", "--noEmit"])
+    keys = ("Check time", "Files:", "Lines:", "Nodes:")
+    lines = [line for line in result.splitlines() if any(k in line for k in keys)]
+    if lines:
+        for line in lines:
             print(f"  {line}")
     else:
         print("  ⚠️ Could not measure performance")

package/bundled-skills/waf-setup/SKILL.md

@@ -118,7 +118,7 @@ aws wafv2 create-web-acl \
     "Priority": 5,
     "Statement": {
       "GeoMatchStatement": {
-        "CountryCodes": ["KP", "IR", "SY"]
+        "CountryCodes": ["KP", "IR"]
       }
     },
     "Action": { "Block": {} },

package/bundled-skills/web3-rate-limiting-circuit-breaker/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: web3-rate-limiting-circuit-breaker
+description: 'On-chain and relayer rate-limiting circuit breaker register: throughput thresholds, emergency pause triggers, and multi-sig recovery.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [security, rate-limiting, circuit-breaker, defi, infrastructure, web3]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Web3 Rate-Limiting & Circuit Breakers
+
+**What it is:** Establishes automated defensive circuit breakers, rate-limiting windows, and volume surge throttles across Web3 smart contracts and relayers.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Web3 Rate-Limiting & Circuit Breakers** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Web3 Rate-Limiting & Circuit Breakers.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Breaker Policy ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `CB-001` |
+| 2 | Target Service / Protocol | `text` | `VARCHAR(64)` | `string` | Text | `Soroban Minting Endpoint` |
+| 3 | Rate Limit Window Seconds | `number` | `INTEGER` | `number` | Number | `60` |
+| 4 | Max Requests Allowed Per Window | `number` | `INTEGER` | `number` | Number | `10` |
+| 5 | Volume Spike Surge Cap % | `number` | `NUMERIC(6,2)` | `number` | Number | `300.00` |
+| 6 | Circuit Breaker Trigger | `select` | `VARCHAR(64)` | `string` | Select | `Automated Anomaly Detection` |
+| 7 | Emergency Pause Activated | `select` | `VARCHAR(16)` | `string` | Select | `No` |
+| 8 | Multi-Sig Unfreeze Required | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 9 | Cooldown Duration Minutes | `number` | `INTEGER` | `number` | Number | `30` |
+| 10 | Breaker Operational State | `select` | `VARCHAR(32)` | `string` | Select | `Guarded Normal` |
+| 11 | Configuration Audit Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Circuit Breaker Trigger**
+
+```
+Automated Anomaly Detection | Price Oracle Divergence | Drain Threshold Exceeded | Manual Admin
+```
+
+**Emergency Pause Activated**
+
+```
+Yes | No
+```
+
+**Multi-Sig Unfreeze Required**
+
+```
+Yes | No
+```
+
+**Breaker Operational State**
+
+```
+Guarded Normal | Tripped (Paused) | Cooldown Recovery | Bypass Mode
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Web3 Rate-Limiting & Circuit Breakers for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+- @smart-contract-formal-verification - verifies state invariants mathematically.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Web3 Rate-Limiting & Circuit Breakers register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/web3-transaction-relayer-pool/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: web3-transaction-relayer-pool
+description: 'Gasless transaction relayer node pool register: fee sponsorship limits, nonce synchronization, and balance replenishment alerts.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [web3, relayer, gasless, meta-transactions, stellar, infrastructure]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Web3 Transaction Relayer Pool Management
+
+**What it is:** Coordinates sponsored meta-transaction nodes, fee reservation pools, and cryptographic nonce tracking for frictionless Web3 user onboarding.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Web3 Transaction Relayer Pool Management** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Web3 Transaction Relayer Pool Management.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Relayer Node ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `RELAY-001` |
+| 2 | Relayer Public Key | `text` | `VARCHAR(56)` | `string` | Text | `GRLY...` |
+| 3 | Network Environment | `select` | `VARCHAR(32)` | `string` | Select | `Stellar Public Mainnet` |
+| 4 | Fee Reserve Balance XLM | `currency` | `NUMERIC(14,7)` | `number` | Number | `450.0000000` |
+| 5 | Min Balance Alert Threshold | `currency` | `NUMERIC(14,7)` | `number` | Number | `50.0000000` |
+| 6 | Daily Sponsored Tx Limit | `number` | `INTEGER` | `number` | Number | `5000` |
+| 7 | Current Day Tx Count | `number` | `INTEGER` | `number` | Number | `1240` |
+| 8 | Max Fee Bps Per Operation | `number` | `INTEGER` | `number` | Number | `100` |
+| 9 | Relayer Operational Health | `select` | `VARCHAR(32)` | `string` | Select | `Active Online` |
+| 10 | Automatic Rebalance Enabled | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 11 | Last Health Ping Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Network Environment**
+
+```
+Stellar Public Mainnet | Stellar Testnet | Ethereum Mainnet | Arbitrum One
+```
+
+**Relayer Operational Health**
+
+```
+Active Online | Low Balance Warning | Nonce Desync | Offline Paused
+```
+
+**Automatic Rebalance Enabled**
+
+```
+Yes | No
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Web3 Transaction Relayer Pool Management for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+- @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Web3 Transaction Relayer Pool Management register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/youtube-summarizer/SKILL.md

@@ -312,10 +312,10 @@ echo "[████████████████████] 100% - Step
 ```markdown
 # [Video Title]
 
-**Canal:** [Channel Name]  
-**Duração:** [Duration]  
+**Channel:** [Channel Name]  
+**Duration:** [Duration]  
 **URL:** [https://youtube.com/watch?v=VIDEO_ID]  
-**Data de Publicação:** [Date if available]
+**Published:** [Date if available]
 
 
 ## 📝 Detailed Summary