@oriro/orirocli 0.1.11 → 0.3.1

package/skills/technical/secrets-management/SKILL.md

@@ -1,135 +1,135 @@
----
-watermark: ORIRO
-name: secrets-management
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-
-
-
-
-
-
-
-  Secrets and configuration management — environment variables, secret stores, rotation, and security best practices for credentials.
-
-
-  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
----
-
-# Secrets and Configuration Management
-
-## The non-negotiable rules
-
-**Never commit secrets to version control.** Ever.
-**Never log secrets.** Logs are often less secured than applications.
-**Never put secrets in URLs.** They appear in server logs, browser history, Referer headers.
-**Rotate secrets regularly.** Especially after any potential exposure.
-
-### .gitignore baseline
-
-```
-.env
-.env.local
-.env.*.local
-*.pem
-*.key
-service-account.json
-*-credentials.json
-```
-
-## Environment variables (baseline)
-
-### Local development
-
-```bash
-# .env.local (not committed)
-DATABASE_URL="postgresql://localhost:5432/myapp_dev"
-STRIPE_SECRET_KEY="sk_test_..."  # Always use test keys locally
-ANTHROPIC_API_KEY="sk-ant-..."
-JWT_SECRET="development-secret-change-in-production"
-```
-
-### Production environments
-
-**Platform env vars:** Vercel, Railway, Render, Heroku — set in dashboard. Never exposed in code.
-**Validate on startup:**
-
-```ts
-// lib/env.ts — fail fast if required secrets missing
-import { z } from "zod";
-
-const envSchema = z.object({
-  DATABASE_URL: z.string().url(),
-  STRIPE_SECRET_KEY: z.string().startsWith("sk_"),
-  ANTHROPIC_API_KEY: z.string().startsWith("sk-ant-"),
-  JWT_SECRET: z.string().min(32),
-  NODE_ENV: z.enum(["development", "production", "test"]).default("development"),
-});
-
-export const env = envSchema.parse(process.env);
-// If any required variable missing: throws at startup with clear error
-```
-
-## Secret stores (for scale)
-
-### HashiCorp Vault
-
-Open source or cloud. Centralized secret storage with access control, rotation, audit logs.
-
-```bash
-# Store secret
-vault kv put secret/myapp/prod stripe_key=sk_live_...
-
-# Read secret
-vault kv get -field=stripe_key secret/myapp/prod
-```
-
-### Cloud provider secret managers
-
-**AWS Secrets Manager:** Native AWS. Auto-rotation. IAM-controlled access.
-**GCP Secret Manager:** Native GCP. IAM-controlled. Versioned.
-**Azure Key Vault:** Native Azure. Hardware security module option.
-
-```ts
-// GCP Secret Manager (example)
-import { SecretManagerServiceClient } from "@google-cloud/secret-manager";
-
-const client = new SecretManagerServiceClient();
-
-async function getSecret(secretName: string): Promise<string> {
-  const name = `projects/${projectId}/secrets/${secretName}/versions/latest`;
-  const [version] = await client.accessSecretVersion({ name });
-  return version.payload!.data!.toString();
-}
-```
-
-## Secret rotation
-
-### Rotation strategy
-
-1. Create new secret value.
-2. Update secret store.
-3. Redeploy application(s) reading the new value.
-4. Verify new value works.
-5. Revoke old value.
-
-**For API keys:** Create new key in provider → deploy new key → verify → revoke old.
-**For database passwords:** Most cloud databases support rotation without downtime via a rotation Lambda/function.
-
-### When to rotate
-
-- Immediately: Key exposed (committed to git, sent in Slack/email, logged).
-- Regularly: Every 90 days for high-value secrets. Some compliance frameworks require this.
-- On personnel change: When engineer with access leaves.
-
-## Service accounts and access control
-
-**Principle of least privilege:** Each service gets only the permissions it needs. Nothing more.
-**Separate credentials per environment:** Production DB never uses same credentials as development.
-**No shared credentials:** Each service has its own API key. If one is compromised, others aren't.
-**Audit access:** Log who accessed what secret and when (built into Vault, AWS Secrets Manager, GCP Secret Manager).
-
-Sources: HashiCorp Vault documentation (vaultproject.io — free), AWS Secrets Manager docs (free), GCP Secret Manager docs (free), OWASP Secrets Management Cheat Sheet (free)
+---
+watermark: ORIRO
+name: secrets-management
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+
+
+
+
+
+
+
+  Secrets and configuration management — environment variables, secret stores, rotation, and security best practices for credentials.
+
+
+  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
+---
+
+# Secrets and Configuration Management
+
+## The non-negotiable rules
+
+**Never commit secrets to version control.** Ever.
+**Never log secrets.** Logs are often less secured than applications.
+**Never put secrets in URLs.** They appear in server logs, browser history, Referer headers.
+**Rotate secrets regularly.** Especially after any potential exposure.
+
+### .gitignore baseline
+
+```
+.env
+.env.local
+.env.*.local
+*.pem
+*.key
+service-account.json
+*-credentials.json
+```
+
+## Environment variables (baseline)
+
+### Local development
+
+```bash
+# .env.local (not committed)
+DATABASE_URL="postgresql://localhost:5432/myapp_dev"
+STRIPE_SECRET_KEY="sk_test_..."  # Always use test keys locally
+ANTHROPIC_API_KEY="sk-ant-..."
+JWT_SECRET="development-secret-change-in-production"
+```
+
+### Production environments
+
+**Platform env vars:** Vercel, Railway, Render, Heroku — set in dashboard. Never exposed in code.
+**Validate on startup:**
+
+```ts
+// lib/env.ts — fail fast if required secrets missing
+import { z } from "zod";
+
+const envSchema = z.object({
+  DATABASE_URL: z.string().url(),
+  STRIPE_SECRET_KEY: z.string().startsWith("sk_"),
+  ANTHROPIC_API_KEY: z.string().startsWith("sk-ant-"),
+  JWT_SECRET: z.string().min(32),
+  NODE_ENV: z.enum(["development", "production", "test"]).default("development"),
+});
+
+export const env = envSchema.parse(process.env);
+// If any required variable missing: throws at startup with clear error
+```
+
+## Secret stores (for scale)
+
+### HashiCorp Vault
+
+Open source or cloud. Centralized secret storage with access control, rotation, audit logs.
+
+```bash
+# Store secret
+vault kv put secret/myapp/prod stripe_key=sk_live_...
+
+# Read secret
+vault kv get -field=stripe_key secret/myapp/prod
+```
+
+### Cloud provider secret managers
+
+**AWS Secrets Manager:** Native AWS. Auto-rotation. IAM-controlled access.
+**GCP Secret Manager:** Native GCP. IAM-controlled. Versioned.
+**Azure Key Vault:** Native Azure. Hardware security module option.
+
+```ts
+// GCP Secret Manager (example)
+import { SecretManagerServiceClient } from "@google-cloud/secret-manager";
+
+const client = new SecretManagerServiceClient();
+
+async function getSecret(secretName: string): Promise<string> {
+  const name = `projects/${projectId}/secrets/${secretName}/versions/latest`;
+  const [version] = await client.accessSecretVersion({ name });
+  return version.payload!.data!.toString();
+}
+```
+
+## Secret rotation
+
+### Rotation strategy
+
+1. Create new secret value.
+2. Update secret store.
+3. Redeploy application(s) reading the new value.
+4. Verify new value works.
+5. Revoke old value.
+
+**For API keys:** Create new key in provider → deploy new key → verify → revoke old.
+**For database passwords:** Most cloud databases support rotation without downtime via a rotation Lambda/function.
+
+### When to rotate
+
+- Immediately: Key exposed (committed to git, sent in Slack/email, logged).
+- Regularly: Every 90 days for high-value secrets. Some compliance frameworks require this.
+- On personnel change: When engineer with access leaves.
+
+## Service accounts and access control
+
+**Principle of least privilege:** Each service gets only the permissions it needs. Nothing more.
+**Separate credentials per environment:** Production DB never uses same credentials as development.
+**No shared credentials:** Each service has its own API key. If one is compromised, others aren't.
+**Audit access:** Log who accessed what secret and when (built into Vault, AWS Secrets Manager, GCP Secret Manager).
+
+Sources: HashiCorp Vault documentation (vaultproject.io — free), AWS Secrets Manager docs (free), GCP Secret Manager docs (free), OWASP Secrets Management Cheat Sheet (free)

package/skills/technical/seo-technical/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-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.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+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.

package/skills/technical/seo-technical/SKILL.md

@@ -1,136 +1,136 @@
----
-watermark: ORIRO
-name: seo-technical
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-  Technical SEO — crawlability, Core Web Vitals, structured data, sitemaps, robots.txt, canonical URLs, and SEO for web apps.
-
-
-
-
-
-
-
-
-
-
-
-  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
----
-
-# Technical SEO
-
-## Crawlability and indexability
-
-### robots.txt
-
-```
-User-agent: *
-Allow: /
-Disallow: /admin/
-Disallow: /api/
-Disallow: /_next/
-
-# Google News specific
-User-agent: Googlebot-News
-Allow: /news/
-
-Sitemap: https://example.com/sitemap.xml
-```
-
-Test at: Google Search Console → URL Inspection tool.
-
-### Sitemap
-
-```xml
-<?xml version="1.0" encoding="UTF-8"?>
-<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
-  <url>
-    <loc>https://example.com/</loc>
-    <lastmod>2024-01-15</lastmod>
-    <changefreq>weekly</changefreq>
-    <priority>1.0</priority>
-  </url>
-</urlset>
-```
-
-Submit to: Google Search Console + Bing Webmaster Tools.
-Auto-generate in Next.js: `app/sitemap.ts` returns `MetadataRoute.Sitemap`.
-
-### Canonical URLs
-
-Prevent duplicate content penalties.
-
-```html
-<link rel="canonical" href="https://example.com/page" />
-```
-
-Use when: Content accessible at multiple URLs (UTM params, sort orders, pagination).
-
-## Core Web Vitals
-
-### LCP (Largest Contentful Paint) — target < 2.5s
-
-Optimize: Preload LCP image, server response time, critical CSS inline.
-
-```html
-<!-- Preload LCP image -->
-<link rel="preload" fetchpriority="high" as="image" href="/hero.webp" />
-```
-
-### INP (Interaction to Next Paint) — target < 200ms
-
-Replace FID from March 2024. Measures responsiveness to all interactions.
-Optimize: Reduce long tasks (> 50ms), defer non-critical JavaScript.
-
-### CLS (Cumulative Layout Shift) — target < 0.1
-
-Optimize: Set explicit width/height on images and embeds, avoid inserting content above existing.
-
-```html
-<!-- Always include dimensions to reserve space -->
-<img src="..." width="800" height="450" alt="..." />
-```
-
-## Structured data
-
-Enables rich results in Google (review stars, FAQs, recipes, breadcrumbs).
-
-```html
-<script type="application/ld+json">
-  {
-    "@context": "https://schema.org",
-    "@type": "Article",
-    "headline": "Article Title",
-    "author": { "@type": "Person", "name": "Author Name" },
-    "datePublished": "2024-01-15",
-    "image": "https://example.com/image.jpg",
-    "publisher": {
-      "@type": "Organization",
-      "name": "Site Name",
-      "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
-    }
-  }
-</script>
-```
-
-Test: Google Rich Results Test (search.google.com/test/rich-results).
-
-## SEO for JavaScript apps
-
-**Problem:** Googlebot may not execute JavaScript well/quickly.
-**Solution:** Server-side rendering (Next.js, Nuxt) or Static Site Generation.
-**Check:** Use `Cache: no-store` during development and view Google's rendered version in Search Console.
-**Next.js app router:** All pages server-rendered by default. No extra work needed.
-
-## Core SEO on-page factors
-
-**Title tag:** 50-60 characters. Primary keyword. Each page unique.
-**Meta description:** 120-160 characters. Call to action. Not a ranking factor but affects CTR.
-**H1:** One per page. Contains primary keyword. Matches search intent.
-**Content quality:** Comprehensive, original, satisfies search intent. Length varies by keyword.
-**Internal linking:** Link related pages together. Helps crawling and distributes authority.
-**Page speed:** Both a ranking factor and UX factor. See performance-optimization skill.
-
-Sources: Google Search Central documentation (developers.google.com/search — free), web.dev SEO (free), Core Web Vitals documentation (web.dev/vitals — free)
+---
+watermark: ORIRO
+name: seo-technical
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+  Technical SEO — crawlability, Core Web Vitals, structured data, sitemaps, robots.txt, canonical URLs, and SEO for web apps.
+
+
+
+
+
+
+
+
+
+
+
+  Sources: Google Search Central, GDPR text, AWS security documentation, Stripe API docs.
+---
+
+# Technical SEO
+
+## Crawlability and indexability
+
+### robots.txt
+
+```
+User-agent: *
+Allow: /
+Disallow: /admin/
+Disallow: /api/
+Disallow: /_next/
+
+# Google News specific
+User-agent: Googlebot-News
+Allow: /news/
+
+Sitemap: https://example.com/sitemap.xml
+```
+
+Test at: Google Search Console → URL Inspection tool.
+
+### Sitemap
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+  <url>
+    <loc>https://example.com/</loc>
+    <lastmod>2024-01-15</lastmod>
+    <changefreq>weekly</changefreq>
+    <priority>1.0</priority>
+  </url>
+</urlset>
+```
+
+Submit to: Google Search Console + Bing Webmaster Tools.
+Auto-generate in Next.js: `app/sitemap.ts` returns `MetadataRoute.Sitemap`.
+
+### Canonical URLs
+
+Prevent duplicate content penalties.
+
+```html
+<link rel="canonical" href="https://example.com/page" />
+```
+
+Use when: Content accessible at multiple URLs (UTM params, sort orders, pagination).
+
+## Core Web Vitals
+
+### LCP (Largest Contentful Paint) — target < 2.5s
+
+Optimize: Preload LCP image, server response time, critical CSS inline.
+
+```html
+<!-- Preload LCP image -->
+<link rel="preload" fetchpriority="high" as="image" href="/hero.webp" />
+```
+
+### INP (Interaction to Next Paint) — target < 200ms
+
+Replace FID from March 2024. Measures responsiveness to all interactions.
+Optimize: Reduce long tasks (> 50ms), defer non-critical JavaScript.
+
+### CLS (Cumulative Layout Shift) — target < 0.1
+
+Optimize: Set explicit width/height on images and embeds, avoid inserting content above existing.
+
+```html
+<!-- Always include dimensions to reserve space -->
+<img src="..." width="800" height="450" alt="..." />
+```
+
+## Structured data
+
+Enables rich results in Google (review stars, FAQs, recipes, breadcrumbs).
+
+```html
+<script type="application/ld+json">
+  {
+    "@context": "https://schema.org",
+    "@type": "Article",
+    "headline": "Article Title",
+    "author": { "@type": "Person", "name": "Author Name" },
+    "datePublished": "2024-01-15",
+    "image": "https://example.com/image.jpg",
+    "publisher": {
+      "@type": "Organization",
+      "name": "Site Name",
+      "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
+    }
+  }
+</script>
+```
+
+Test: Google Rich Results Test (search.google.com/test/rich-results).
+
+## SEO for JavaScript apps
+
+**Problem:** Googlebot may not execute JavaScript well/quickly.
+**Solution:** Server-side rendering (Next.js, Nuxt) or Static Site Generation.
+**Check:** Use `Cache: no-store` during development and view Google's rendered version in Search Console.
+**Next.js app router:** All pages server-rendered by default. No extra work needed.
+
+## Core SEO on-page factors
+
+**Title tag:** 50-60 characters. Primary keyword. Each page unique.
+**Meta description:** 120-160 characters. Call to action. Not a ranking factor but affects CTR.
+**H1:** One per page. Contains primary keyword. Matches search intent.
+**Content quality:** Comprehensive, original, satisfies search intent. Length varies by keyword.
+**Internal linking:** Link related pages together. Helps crawling and distributes authority.
+**Page speed:** Both a ranking factor and UX factor. See performance-optimization skill.
+
+Sources: Google Search Central documentation (developers.google.com/search — free), web.dev SEO (free), Core Web Vitals documentation (web.dev/vitals — free)

package/skills/technical/technical-writing/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 ORIRO.ai
-
-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.
+MIT License
+
+Copyright (c) 2026 ORIRO.ai
+
+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.