opencode-skills-collection 4.1.3 → 4.1.5

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/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/zk-proof-verification-pipeline/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: zk-proof-verification-pipeline
+description: 'Zero-knowledge cryptographic verification pipeline register: proving system, circuit verification keys, public inputs, and gas costs.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [zk, zero-knowledge, snark, cryptography, privacy, soroban, web3]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Zero-Knowledge Proof Verification Pipeline
+
+**What it is:** Registers zero-knowledge SNARK proof verification keys, circuit complexity constraints, and nullifier tracking to prevent double-spending in privacy systems.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Zero-Knowledge Proof Verification Pipeline** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Zero-Knowledge Proof Verification Pipeline.
+- 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 | ZK Verification ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `ZK-001` |
+| 2 | Proving System Architecture | `select` | `VARCHAR(64)` | `string` | Select | `Groth16 (BN254)` |
+| 3 | Circuit Identifier | `text` | `VARCHAR(64)` | `string` | Text | `private_identity_membership` |
+| 4 | Public Inputs Count | `number` | `INTEGER` | `number` | Number | `4` |
+| 5 | Verification Key Hash | `text` | `VARCHAR(64)` | `string` | Text | `0x98f4a...` |
+| 6 | Proof Generation Time Ms | `number` | `INTEGER` | `number` | Number | `420` |
+| 7 | On-Chain Verification Gas | `number` | `INTEGER` | `number` | Number | `185000` |
+| 8 | Nullifier Collision Checked | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 9 | Proof Verification Verdict | `select` | `VARCHAR(32)` | `string` | Select | `Cryptographically Valid` |
+| 10 | Cryptographer Reviewer | `text` | `VARCHAR(64)` | `string` | Text | `Ranjeet2063` |
+| 11 | Verification Timestamp | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Proving System Architecture**
+
+```
+Groth16 (BN254) | Plonk (KZG) | Halo2 | STARK
+```
+
+**Nullifier Collision Checked**
+
+```
+Yes | No
+```
+
+**Proof Verification Verdict**
+
+```
+Cryptographically Valid | Invalid Proof State | Malformed Inputs
+```
+
+## 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 Zero-Knowledge Proof Verification Pipeline 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
+
+- @smart-contract-formal-verification - verifies state invariants mathematically.
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Zero-Knowledge Proof Verification Pipeline register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "4.1.3",
+  "version": "4.1.5",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",