@oriro/orirocli 0.1.11 → 0.3.1

package/skills/technical/cloud-architecture/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/cloud-architecture/SKILL.md

@@ -1,85 +1,85 @@
----
-watermark: ORIRO
-name: cloud-architecture
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-  Cloud architecture — serverless, containers, managed services, cost optimization, availability, and cloud design patterns.
-
-
-
-  Sources: Technical documentation, public guidelines, industry best practices.
----
-
-# Cloud Architecture
-
-## Serverless vs. containers vs. VMs
-
-|                | Serverless                     | Containers                   | VMs                |
-| -------------- | ------------------------------ | ---------------------------- | ------------------ |
-| **Startup**    | Cold starts (ms-s)             | Fast (ms)                    | Slow (min)         |
-| **Scale**      | 0 to ∞ automatically           | Scale to preset max          | Manual or auto     |
-| **Cost model** | Per invocation                 | Per running container        | Per hour running   |
-| **Management** | None                           | Some                         | Most               |
-| **Best for**   | Event-driven, variable traffic | Stateful apps, microservices | Legacy, compliance |
-
-## Serverless patterns (AWS Lambda / Cloud Run / Vercel Functions)
-
-**When to use:**
-
-- Intermittent or unpredictable traffic
-- Event-driven workloads (file uploads, webhooks)
-- APIs that scale to zero (dev/staging environments)
-
-**When NOT to use:**
-
-- Persistent connections (WebSockets)
-- Long-running jobs (> 15 min for Lambda)
-- Workloads where cold start latency is unacceptable
-
-**Cold start mitigation:** Provisioned concurrency (Lambda), minimum instances (Cloud Run), ping-based warming.
-
-## Key design principles
-
-### High availability
-
-**Multi-AZ deployment:** Replicate across availability zones. Single zone outage (common) = no downtime.
-**Health checks + auto-replacement:** Load balancer removes unhealthy instances. Auto-scaling replaces them.
-**Circuit breakers:** When a downstream service is unhealthy, stop calling it. Fail fast. Retry with backoff.
-
-### Stateless design
-
-Applications should be stateless — any instance can handle any request.
-State stored in: Database, Redis, S3 — NOT in application memory.
-Enables: Horizontal scaling, easy replacement of instances.
-
-### Database patterns for cloud
-
-**Managed databases:** RDS, Cloud SQL, Aurora, PlanetScale. Handles backups, patching, failover.
-**Read replicas:** Scale reads. Primary handles writes.
-**Connection pooling (critical):** PgBouncer or Prisma Data Proxy. Lambda functions must use connection pooling (each invocation opens a new connection otherwise → connection exhaustion).
-**Multi-region:** Active-active (complex) or active-passive (simpler, some recovery time).
-
-## Cost optimization
-
-### Right-sizing
-
-Start with the smallest instance that meets performance requirements.
-Benchmark first. Scale when metrics show the need.
-Reserved instances (1-3 year commitment) for predictable base load: 30-60% savings vs. on-demand.
-Spot instances for fault-tolerant batch workloads: 70-90% savings.
-
-### Storage tiering
-
-S3 Intelligent-Tiering: Automatically moves objects to cheaper storage based on access patterns.
-Archive cold data to Glacier ($0.004/GB vs $0.023/GB Standard).
-Delete what you don't need (surprising how often this is forgotten).
-
-### Architecture for cost
-
-CDN + static assets: Serve from CDN, not from compute.
-Background jobs: Use spot instances or serverless for async work.
-Caching: Redis reduces database calls and compute.
-
-Sources: AWS Well-Architected Framework (aws.amazon.com/architecture/well-architected — free), GCP best practices (cloud.google.com/architecture — free), Azure Architecture Center (free), Cloudflare architecture blog (free)
+---
+watermark: ORIRO
+name: cloud-architecture
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+  Cloud architecture — serverless, containers, managed services, cost optimization, availability, and cloud design patterns.
+
+
+
+  Sources: Technical documentation, public guidelines, industry best practices.
+---
+
+# Cloud Architecture
+
+## Serverless vs. containers vs. VMs
+
+|                | Serverless                     | Containers                   | VMs                |
+| -------------- | ------------------------------ | ---------------------------- | ------------------ |
+| **Startup**    | Cold starts (ms-s)             | Fast (ms)                    | Slow (min)         |
+| **Scale**      | 0 to ∞ automatically           | Scale to preset max          | Manual or auto     |
+| **Cost model** | Per invocation                 | Per running container        | Per hour running   |
+| **Management** | None                           | Some                         | Most               |
+| **Best for**   | Event-driven, variable traffic | Stateful apps, microservices | Legacy, compliance |
+
+## Serverless patterns (AWS Lambda / Cloud Run / Vercel Functions)
+
+**When to use:**
+
+- Intermittent or unpredictable traffic
+- Event-driven workloads (file uploads, webhooks)
+- APIs that scale to zero (dev/staging environments)
+
+**When NOT to use:**
+
+- Persistent connections (WebSockets)
+- Long-running jobs (> 15 min for Lambda)
+- Workloads where cold start latency is unacceptable
+
+**Cold start mitigation:** Provisioned concurrency (Lambda), minimum instances (Cloud Run), ping-based warming.
+
+## Key design principles
+
+### High availability
+
+**Multi-AZ deployment:** Replicate across availability zones. Single zone outage (common) = no downtime.
+**Health checks + auto-replacement:** Load balancer removes unhealthy instances. Auto-scaling replaces them.
+**Circuit breakers:** When a downstream service is unhealthy, stop calling it. Fail fast. Retry with backoff.
+
+### Stateless design
+
+Applications should be stateless — any instance can handle any request.
+State stored in: Database, Redis, S3 — NOT in application memory.
+Enables: Horizontal scaling, easy replacement of instances.
+
+### Database patterns for cloud
+
+**Managed databases:** RDS, Cloud SQL, Aurora, PlanetScale. Handles backups, patching, failover.
+**Read replicas:** Scale reads. Primary handles writes.
+**Connection pooling (critical):** PgBouncer or Prisma Data Proxy. Lambda functions must use connection pooling (each invocation opens a new connection otherwise → connection exhaustion).
+**Multi-region:** Active-active (complex) or active-passive (simpler, some recovery time).
+
+## Cost optimization
+
+### Right-sizing
+
+Start with the smallest instance that meets performance requirements.
+Benchmark first. Scale when metrics show the need.
+Reserved instances (1-3 year commitment) for predictable base load: 30-60% savings vs. on-demand.
+Spot instances for fault-tolerant batch workloads: 70-90% savings.
+
+### Storage tiering
+
+S3 Intelligent-Tiering: Automatically moves objects to cheaper storage based on access patterns.
+Archive cold data to Glacier ($0.004/GB vs $0.023/GB Standard).
+Delete what you don't need (surprising how often this is forgotten).
+
+### Architecture for cost
+
+CDN + static assets: Serve from CDN, not from compute.
+Background jobs: Use spot instances or serverless for async work.
+Caching: Redis reduces database calls and compute.
+
+Sources: AWS Well-Architected Framework (aws.amazon.com/architecture/well-architected — free), GCP best practices (cloud.google.com/architecture — free), Azure Architecture Center (free), Cloudflare architecture blog (free)

package/skills/technical/content-platform/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/content-platform/SKILL.md

@@ -1,134 +1,134 @@
----
-watermark: ORIRO
-disable-model-invocation: true
-name: content-platform
-provider: ORIRO.ai
-copyright: Copyright (c) 2026 ORIRO.ai
-description: >
-
-
-
-
-  Content platform development — CMS, media management, publishing workflows, SEO, and content delivery.
-
-  Sources: Stripe docs, Anthropic docs, Sanity/Contentful docs, industry-specific technical resources.
----
-
-# Content Platform Development
-
-## CMS architecture
-
-### Headless CMS vs. traditional
-
-**Traditional (WordPress):** CMS manages content AND presentation. Coupled.
-**Headless:** CMS manages content only. Exposes content via API. Frontend is separate.
-**Benefits of headless:** Use any frontend framework. Better performance. Multi-channel (web, mobile, voice, IoT).
-
-### Headless CMS options
-
-**Sanity:** Flexible content modeling. Real-time collaboration. GROQ query language. Generous free tier.
-**Contentful:** Enterprise-grade. Strong CDN. Good API.
-**Strapi:** Self-hosted (open source) or cloud. Full customization.
-**Payload:** Code-first headless CMS. TypeScript native. Self-hosted. Growing fast.
-**Directus:** Database-first. Wraps existing database.
-**Notion as CMS:** Via Notion API for simple blogs. Limited but no setup.
-
-### Content modeling (Sanity example)
-
-```ts
-// schemas/post.ts
-export default {
-  name: "post",
-  title: "Blog Post",
-  type: "document",
-  fields: [
-    { name: "title", title: "Title", type: "string", validation: (Rule) => Rule.required() },
-    { name: "slug", title: "Slug", type: "slug", options: { source: "title" } },
-    { name: "publishedAt", title: "Published At", type: "datetime" },
-    { name: "author", title: "Author", type: "reference", to: [{ type: "author" }] },
-    { name: "mainImage", title: "Main Image", type: "image", options: { hotspot: true } },
-    {
-      name: "categories",
-      title: "Categories",
-      type: "array",
-      of: [{ type: "reference", to: [{ type: "category" }] }],
-    },
-    { name: "body", title: "Body", type: "array", of: [{ type: "block" }, { type: "image" }] },
-  ],
-};
-```
-
-## Media management
-
-### Image optimization
-
-```tsx
-// Next.js Image component handles optimization automatically
-import Image from "next/image";
-
-<Image
-  src={imageSrc}
-  alt="Description"
-  width={800}
-  height={450}
-  priority // For above-the-fold images
-  placeholder="blur"
-  blurDataURL={blurDataUrl}
-/>;
-```
-
-**CDN:** Cloudflare Images, Vercel Image Optimization, Cloudinary (transform on-the-fly).
-**Formats:** WebP for photos (25-35% smaller than JPEG). AVIF even smaller but less support.
-**Responsive images:** Different sizes for different screen widths. srcset attribute.
-**Lazy loading:** `loading="lazy"` for below-fold images. Native browser support.
-
-### Video
-
-**Upload:** Direct to Cloudflare Stream, Mux, or Vimeo.
-**Never:** Serve raw video from your own servers at scale.
-**HLS (HTTP Live Streaming):** Adaptive bitrate. Player downloads appropriate quality based on bandwidth.
-**Thumbnails:** Auto-generate at upload. Store in CDN.
-
-## Publishing workflows
-
-### Draft/Published state
-
-```prisma
-model Post {
-  id          String     @id @default(cuid())
-  status      PostStatus @default(DRAFT)  // DRAFT, REVIEW, PUBLISHED, ARCHIVED
-  publishedAt DateTime?
-  scheduledFor DateTime? // Future publish
-}
-```
-
-### Content versioning
-
-Store all edits. Allow rollback to any previous version. Show diff between versions.
-Simple: Store JSON snapshots in a revisions table with authorId and timestamp.
-
-## SEO implementation
-
-```tsx
-// Next.js metadata API
-export async function generateMetadata({ params }): Promise<Metadata> {
-  const post = await getPost(params.slug);
-  return {
-    title: post.title,
-    description: post.excerpt,
-    openGraph: {
-      title: post.title,
-      description: post.excerpt,
-      images: [{ url: post.mainImage.url, width: 1200, height: 630 }],
-    },
-    twitter: { card: "summary_large_image", title: post.title },
-  };
-}
-```
-
-**Structured data (JSON-LD):** Article, BreadcrumbList, FAQPage schemas.
-**Sitemap:** Auto-generated. Include all published content. Update on publish.
-**RSS feed:** Still important for readers and podcast aggregators.
-**Robots.txt:** Control crawler access.
-
-Sources: Sanity documentation (sanity.io/docs — free), Next.js docs (nextjs.org/docs — free), MDN SEO guide (free), web.dev SEO (free)
+---
+watermark: ORIRO
+disable-model-invocation: true
+name: content-platform
+provider: ORIRO.ai
+copyright: Copyright (c) 2026 ORIRO.ai
+description: >
+
+
+
+
+  Content platform development — CMS, media management, publishing workflows, SEO, and content delivery.
+
+  Sources: Stripe docs, Anthropic docs, Sanity/Contentful docs, industry-specific technical resources.
+---
+
+# Content Platform Development
+
+## CMS architecture
+
+### Headless CMS vs. traditional
+
+**Traditional (WordPress):** CMS manages content AND presentation. Coupled.
+**Headless:** CMS manages content only. Exposes content via API. Frontend is separate.
+**Benefits of headless:** Use any frontend framework. Better performance. Multi-channel (web, mobile, voice, IoT).
+
+### Headless CMS options
+
+**Sanity:** Flexible content modeling. Real-time collaboration. GROQ query language. Generous free tier.
+**Contentful:** Enterprise-grade. Strong CDN. Good API.
+**Strapi:** Self-hosted (open source) or cloud. Full customization.
+**Payload:** Code-first headless CMS. TypeScript native. Self-hosted. Growing fast.
+**Directus:** Database-first. Wraps existing database.
+**Notion as CMS:** Via Notion API for simple blogs. Limited but no setup.
+
+### Content modeling (Sanity example)
+
+```ts
+// schemas/post.ts
+export default {
+  name: "post",
+  title: "Blog Post",
+  type: "document",
+  fields: [
+    { name: "title", title: "Title", type: "string", validation: (Rule) => Rule.required() },
+    { name: "slug", title: "Slug", type: "slug", options: { source: "title" } },
+    { name: "publishedAt", title: "Published At", type: "datetime" },
+    { name: "author", title: "Author", type: "reference", to: [{ type: "author" }] },
+    { name: "mainImage", title: "Main Image", type: "image", options: { hotspot: true } },
+    {
+      name: "categories",
+      title: "Categories",
+      type: "array",
+      of: [{ type: "reference", to: [{ type: "category" }] }],
+    },
+    { name: "body", title: "Body", type: "array", of: [{ type: "block" }, { type: "image" }] },
+  ],
+};
+```
+
+## Media management
+
+### Image optimization
+
+```tsx
+// Next.js Image component handles optimization automatically
+import Image from "next/image";
+
+<Image
+  src={imageSrc}
+  alt="Description"
+  width={800}
+  height={450}
+  priority // For above-the-fold images
+  placeholder="blur"
+  blurDataURL={blurDataUrl}
+/>;
+```
+
+**CDN:** Cloudflare Images, Vercel Image Optimization, Cloudinary (transform on-the-fly).
+**Formats:** WebP for photos (25-35% smaller than JPEG). AVIF even smaller but less support.
+**Responsive images:** Different sizes for different screen widths. srcset attribute.
+**Lazy loading:** `loading="lazy"` for below-fold images. Native browser support.
+
+### Video
+
+**Upload:** Direct to Cloudflare Stream, Mux, or Vimeo.
+**Never:** Serve raw video from your own servers at scale.
+**HLS (HTTP Live Streaming):** Adaptive bitrate. Player downloads appropriate quality based on bandwidth.
+**Thumbnails:** Auto-generate at upload. Store in CDN.
+
+## Publishing workflows
+
+### Draft/Published state
+
+```prisma
+model Post {
+  id          String     @id @default(cuid())
+  status      PostStatus @default(DRAFT)  // DRAFT, REVIEW, PUBLISHED, ARCHIVED
+  publishedAt DateTime?
+  scheduledFor DateTime? // Future publish
+}
+```
+
+### Content versioning
+
+Store all edits. Allow rollback to any previous version. Show diff between versions.
+Simple: Store JSON snapshots in a revisions table with authorId and timestamp.
+
+## SEO implementation
+
+```tsx
+// Next.js metadata API
+export async function generateMetadata({ params }): Promise<Metadata> {
+  const post = await getPost(params.slug);
+  return {
+    title: post.title,
+    description: post.excerpt,
+    openGraph: {
+      title: post.title,
+      description: post.excerpt,
+      images: [{ url: post.mainImage.url, width: 1200, height: 630 }],
+    },
+    twitter: { card: "summary_large_image", title: post.title },
+  };
+}
+```
+
+**Structured data (JSON-LD):** Article, BreadcrumbList, FAQPage schemas.
+**Sitemap:** Auto-generated. Include all published content. Update on publish.
+**RSS feed:** Still important for readers and podcast aggregators.
+**Robots.txt:** Control crawler access.
+
+Sources: Sanity documentation (sanity.io/docs — free), Next.js docs (nextjs.org/docs — free), MDN SEO guide (free), web.dev SEO (free)

package/skills/technical/cybersecurity-advanced/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.