natureco-cli 5.18.3 → 5.20.0

package/skills/search-implementation/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: search-implementation
+description: Implement full-text search with Elasticsearch, Meilisearch, or PostgreSQL FTS
+category: Software Development
+---
+
+# Search Implementation
+
+## Overview
+Implement full-text search with Elasticsearch, Meilisearch, or PostgreSQL FTS. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply search implementation best practices
+- When establishing processes or standards for your workflow
+- When training team members on search implementation
+- When automating or optimizing search implementation tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply search implementation for my current project
+Assistant: I'll help you apply search implementation step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/secrets-management/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: secrets-management
+description: Manage secrets with vaults, encryption, rotation policies, and access audit
+category: Software Development
+---
+
+# Secrets Management
+
+## Overview
+Manage secrets with vaults, encryption, rotation policies, and access audit. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply secrets management best practices
+- When establishing processes or standards for your workflow
+- When training team members on secrets management
+- When automating or optimizing secrets management tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply secrets management for my current project
+Assistant: I'll help you apply secrets management step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/secure-linux-web-hosting/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: secure-linux-web-hosting
+description: Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
+---
+
+## Overview
+
+Use this skill to turn a cloud server into a safely reachable web host
+without leaning on stale distro-specific memory or outdated Debian-10-era
+tutorials.
+
+This skill keeps the familiar teaching arc of a beginner-friendly server guide,
+but turns it into a reusable operator workflow:
+
+1. Intake and routing
+2. Prerequisites
+3. Secure access
+4. Firewall and exposure
+5. Web server setup
+6. Static site or app proxy
+7. HTTPS
+8. Validation
+9. Optional advanced tuning
+
+Before giving actionable commands, identify the distro family and verify the
+current package names, service units, config paths, and ACME-client guidance
+against official documentation for the user's distro and chosen tools.
+
+Open [`references/workflow-map.md`](./references/workflow-map.md) first for the
+phase sequence, then open the narrower reference file you need.
+
+## When to Use
+
+Use this skill when the user mentions any of the following:
+
+- a cloud server, VM, droplet, or other Linux host they want to use for hosting
+- connecting a domain or DNS A/AAAA record to a server
+- SSH login, SSH hardening, root login, keys, ports, or firewall setup
+- installing or configuring Nginx for a website
+- serving a simple static site from Linux
+- putting a small app behind Nginx as a reverse proxy
+- HTTPS, Let's Encrypt, Certbot, `acme.sh`, certificate renewal, or redirecting
+  HTTP to HTTPS
+- optional post-setup performance or network tuning such as BBR
+
+Do not use this skill for:
+
+- Kubernetes, PaaS, or full container-orchestrator deployment design
+- application-specific build or CI/CD questions where Linux hosting is not the
+  actual problem
+- Windows or macOS host administration
+- public multi-tenant production architecture reviews that need a broader SRE
+  or platform-design treatment
+
+## Workflow
+
+### 1. Intake and classify the current state
+
+Start by identifying:
+
+- distro family or image name
+- whether the user has root access, an admin user, or only one live SSH session
+- whether DNS already points at the host
+- whether the goal is a static site or an app reverse proxy
+- whether ports are already exposed
+- whether HTTPS is already partially configured
+
+If the distro is unknown, ask for it or have the user inspect `/etc/os-release`
+before giving concrete package or service commands.
+
+### 2. Verify current docs before actionable commands
+
+Use bundled references for routing, then verify details against live official
+docs before giving commands that depend on current distro behavior.
+
+Always verify:
+
+- package manager commands and package names
+- firewall tooling and service names
+- SSH service unit names and config include paths
+- Nginx package and config layout
+- the chosen ACME client's current instructions
+
+If you cannot verify a detail, say so and give high-level guidance instead of
+pretending the old Debian tutorial path is universal.
+
+### 3. Keep the phases in order
+
+Walk through the phases in this order unless the user is explicitly asking for
+review or remediation of an existing setup:
+
+1. prerequisites
+2. secure access
+3. firewall and exposure
+4. web server
+5. choose one hosting branch: static site or app proxy
+6. HTTPS
+7. validation
+8. optional advanced tuning
+
+Do not collapse the static-site branch and reverse-proxy branch into one
+default answer. Pick the branch that matches the user's goal.
+
+### 4. Enforce the safety gates
+
+Treat these as hard stop checks:
+
+- Do not recommend changing SSH port, disabling password auth, or disabling
+  root SSH login until key-based login works in a second SSH session.
+- Do not recommend certificate issuance until DNS resolves to the intended host
+  and the HTTP site or proxy path works as expected.
+- Do not force an HTTP-to-HTTPS redirect until HTTPS loads cleanly.
+- Do not suggest BBR or similar tuning until secure hosting is already working.
+
+Always distinguish:
+
+- local-machine actions: SSH, DNS checks, browser tests
+- server actions: package install, config edits, service reloads, firewall rules
+
+## Output Expectations
+
+For a fresh setup, provide:
+
+- a brief diagnosis of the current state
+- the current phase and why it comes next
+- local-machine steps separate from server steps
+- concrete commands or config snippets only after doc verification
+- a verification step after each risky change
+- a short "if this fails, check X" branch for the likely mistake at that phase
+
+For a hardening or troubleshooting review, provide:
+
+- the most likely risk or breakage first
+- a prioritized remediation sequence
+- the first safe verification step before the next config change
+
+## Common Mistakes
+
+- treating Debian-specific commands from an old article as Linux-universal
+- hardening SSH in the only active session and locking the user out
+- opening application ports directly instead of keeping the app on loopback
+- mixing static-file hosting guidance and reverse-proxy guidance in one config
+- attempting ACME issuance before DNS or HTTP is actually correct
+- forcing redirects before HTTPS is proven
+- treating BBR as part of the core setup instead of an optional later step
+- ignoring SELinux or AppArmor differences when Nginx can read files on one
+  distro but not another
+
+## Reference Usage
+
+Use [`references/workflow-map.md`](./references/workflow-map.md) for the phase map,
+branching logic, and validation order.
+
+Use [`references/distro-routing.md`](./references/distro-routing.md) when distro
+family, package manager, firewall tooling, or config layout matters.
+
+Use [`references/nginx-patterns.md`](./references/nginx-patterns.md) when the user
+needs the static-site branch or the reverse-proxy branch.
+
+Use [`references/security-and-tls.md`](./references/security-and-tls.md) for SSH
+hardening sequence, firewall posture, certificate issuance, renewal, and
+redirect timing.

package/skills/security-audit/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: security-audit
+description: Audit code for OWASP Top 10 vulnerabilities, dependency risks, and secret leaks
+category: Software Development
+---
+
+# Security Audit
+
+## Overview
+Audit code for OWASP Top 10 vulnerabilities, dependency risks, and secret leaks. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply security audit best practices
+- When establishing processes or standards for your workflow
+- When training team members on security audit
+- When automating or optimizing security audit tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply security audit for my current project
+Assistant: I'll help you apply security audit step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/selective-memory/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: selective-memory
+description: Store only high-signal memories by filtering trivial interactions and deduplicating facts
+category: Token Savings
+---
+
+# Selective Memory
+
+## Overview
+Store only high-signal memories by filtering trivial interactions and deduplicating facts. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply selective memory best practices
+- When establishing processes or standards for your workflow
+- When training team members on selective memory
+- When automating or optimizing selective memory tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply selective memory for my current project
+Assistant: I'll help you apply selective memory step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/semantic-search/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: semantic-search
+description: Implement semantic search with dense/sparse embeddings and hybrid ranking
+category: AI Agents
+---
+
+# Semantic Search
+
+## Overview
+Implement semantic search with dense/sparse embeddings and hybrid ranking. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply semantic search best practices
+- When establishing processes or standards for your workflow
+- When training team members on semantic search
+- When automating or optimizing semantic search tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply semantic search for my current project
+Assistant: I'll help you apply semantic search step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/semantic-versioning/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: semantic-versioning
+description: Apply semantic versioning with breaking change detection and automated release notes
+category: Software Development
+---
+
+# Semantic Versioning
+
+## Overview
+Apply semantic versioning with breaking change detection and automated release notes. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply semantic versioning best practices
+- When establishing processes or standards for your workflow
+- When training team members on semantic versioning
+- When automating or optimizing semantic versioning tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply semantic versioning for my current project
+Assistant: I'll help you apply semantic versioning step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/sentiment-analysis/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: sentiment-analysis
+description: Analyze sentiment with polarity scoring, aspect-based analysis, and emotion detection
+category: AI Agents
+---
+
+# Sentiment Analysis
+
+## Overview
+Analyze sentiment with polarity scoring, aspect-based analysis, and emotion detection. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply sentiment analysis best practices
+- When establishing processes or standards for your workflow
+- When training team members on sentiment analysis
+- When automating or optimizing sentiment analysis tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply sentiment analysis for my current project
+Assistant: I'll help you apply sentiment analysis step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/seo-optimization/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: seo-optimization
+description: Optimize for search engines with meta tags, structured data, sitemaps, and SSR
+category: Software Development
+---
+
+# Seo Optimization
+
+## Overview
+Optimize for search engines with meta tags, structured data, sitemaps, and SSR. This skill helps you apply structured, repeatable methods for consistent results.
+
+## When to Use
+- When you need to apply seo optimization best practices
+- When establishing processes or standards for your workflow
+- When training team members on seo optimization
+- When automating or optimizing seo optimization tasks
+
+## Instructions
+1. **Assess**: Evaluate the current state, requirements, and constraints
+2. **Plan**: Define the approach, steps, and success criteria
+3. **Execute**: Follow the established patterns and best practices
+4. **Verify**: Check results against expected outcomes and quality standards
+5. **Iterate**: Refine based on feedback and lessons learned
+
+## Examples
+```
+User: Help me apply seo optimization for my current project
+Assistant: I'll help you apply seo optimization step by step...
+```
+
+## Related Skills
+- Use with `workflow` tool for orchestrated execution
+- Combine with `task` tool for delegated processing
+- Reference `system-prompt` for system-level integration

package/skills/setup-pre-commit/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: setup-pre-commit
+description: Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
+---
+
+# Setup Pre-Commit Hooks
+
+## What This Sets Up
+
+- **Husky** pre-commit hook
+- **lint-staged** running Prettier on all staged files
+- **Prettier** config (if missing)
+- **typecheck** and **test** scripts in the pre-commit hook
+
+## Steps
+
+### 1. Detect package manager
+
+Check for `package-lock.json` (npm), `pnpm-lock.yaml` (pnpm), `yarn.lock` (yarn), `bun.lockb` (bun). Use whichever is present. Default to npm if unclear.
+
+### 2. Install dependencies
+
+Install as devDependencies:
+
+```
+husky lint-staged prettier
+```
+
+### 3. Initialize Husky
+
+```bash
+npx husky init
+```
+
+This creates `.husky/` dir and adds `prepare: "husky"` to package.json.
+
+### 4. Create `.husky/pre-commit`
+
+Write this file (no shebang needed for Husky v9+):
+
+```
+npx lint-staged
+npm run typecheck
+npm run test
+```
+
+**Adapt**: Replace `npm` with detected package manager. If repo has no `typecheck` or `test` script in package.json, omit those lines and tell the user.
+
+### 5. Create `.lintstagedrc`
+
+```json
+{
+  "*": "prettier --ignore-unknown --write"
+}
+```
+
+### 6. Create `.prettierrc` (if missing)
+
+Only create if no Prettier config exists. Use these defaults:
+
+```json
+{
+  "useTabs": false,
+  "tabWidth": 2,
+  "printWidth": 80,
+  "singleQuote": false,
+  "trailingComma": "es5",
+  "semi": true,
+  "arrowParens": "always"
+}
+```
+
+### 7. Verify
+
+- [ ] `.husky/pre-commit` exists and is executable
+- [ ] `.lintstagedrc` exists
+- [ ] `prepare` script in package.json is `"husky"`
+- [ ] `prettier` config exists
+- [ ] Run `npx lint-staged` to verify it works
+
+### 8. Commit
+
+Stage all changed/created files and commit with message: `Add pre-commit hooks (husky + lint-staged + prettier)`
+
+This will run through the new pre-commit hooks — a good smoke test that everything works.
+
+## Notes
+
+- Husky v9+ doesn't need shebangs in hook files
+- `prettier --ignore-unknown` skips files Prettier can't parse (images, etc.)
+- The pre-commit runs lint-staged first (fast, staged-only), then full typecheck and tests