@khalidsaidi/skillrunner 0.1.2 → 0.1.3

package/dist/registry/skills/openai-netlify-deploy/upstream/references/deployment-patterns.md

@@ -0,0 +1,303 @@
+# Netlify Deployment Patterns
+
+Common deployment scenarios and best practices for the Netlify skill.
+
+## Deployment Decision Tree
+
+```
+Is user authenticated?
+├─ No → Run `netlify login`
+└─ Yes → Is site linked?
+    ├─ No → Is it a Git repo?
+    │   ├─ Yes → Try `netlify link --git-remote-url`
+    │   │   ├─ Success → Continue to deploy
+    │   │   └─ Fail → Run `netlify init`
+    │   └─ No → Run `netlify init`
+    └─ Yes → Is this first deploy or existing site?
+        ├─ First deploy/new site → `netlify deploy --prod`
+        └─ Existing site → `netlify deploy` (preview)
+```
+
+## Scenario 1: First-Time Deployment (New Project)
+
+**Context**: User has a project that has never been deployed to Netlify.
+
+**Steps**:
+1. Check authentication: `npx netlify status`
+2. If not authenticated: `npx netlify login`
+3. Initialize new site: `npx netlify init`
+   - This guides user through setup
+   - Creates netlify.toml if needed
+4. Install dependencies: `npm install`
+5. Deploy to production: `npx netlify deploy --prod`
+
+**Example**:
+```bash
+npx netlify status
+# Not linked to a site
+
+npx netlify login
+# Opens browser for authentication
+
+npx netlify init
+# Walks through site creation
+
+npm install
+npx netlify deploy --prod
+```
+
+## Scenario 2: Linking Existing Git Repository to Existing Site
+
+**Context**: User has a site already on Netlify and wants to link their local repo.
+
+**Steps**:
+1. Check authentication: `npx netlify status`
+2. Get Git remote: `git remote show origin`
+3. Extract URL (e.g., `https://github.com/user/repo.git`)
+4. Link by remote: `npx netlify link --git-remote-url <URL>`
+5. If found, linked. If not, run `netlify init`
+
+**Example**:
+```bash
+git remote show origin
+# * remote origin
+#   Fetch URL: https://github.com/user/my-app.git
+
+npx netlify link --git-remote-url https://github.com/user/my-app.git
+# Site linked successfully
+```
+
+## Scenario 3: Preview Deployment (Testing Changes)
+
+**Context**: User wants to test changes before pushing to production.
+
+**Steps**:
+1. Ensure site is linked: `npx netlify status`
+2. Make code changes
+3. Deploy preview: `npx netlify deploy`
+4. Review preview URL
+5. If approved, deploy to prod: `npx netlify deploy --prod`
+
+**Example**:
+```bash
+# Make changes to code
+
+npx netlify deploy
+# Draft deploy URL: https://507f1f77bcf86cd799439011-my-app.netlify.app
+
+# Test the preview, then:
+npx netlify deploy --prod
+```
+
+## Scenario 4: Framework-Specific Deployments
+
+### Next.js
+
+```bash
+# Next.js typically uses .next as output
+npx netlify deploy --prod
+
+# netlify.toml should have:
+# [build]
+#   command = "npm run build"
+#   publish = ".next"
+```
+
+### React (Vite)
+
+```bash
+# Vite outputs to dist by default
+npm run build
+npx netlify deploy --dir=dist --prod
+
+# netlify.toml:
+# [build]
+#   command = "npm run build"
+#   publish = "dist"
+```
+
+### Static HTML
+
+```bash
+# No build step needed
+npx netlify deploy --dir=. --prod
+```
+
+## Scenario 5: Monorepo Deployment
+
+**Context**: Project is in a subdirectory of a monorepo.
+
+**Steps**:
+1. Navigate to project subdirectory: `cd packages/frontend`
+2. Or set base in netlify.toml:
+   ```toml
+   [build]
+     base = "packages/frontend"
+     command = "npm run build"
+     publish = "dist"
+   ```
+3. Deploy normally: `npx netlify deploy --prod`
+
+## Scenario 6: Environment Variables
+
+**Context**: Project needs secrets or environment-specific config.
+
+**Steps**:
+1. Never commit secrets to Git
+2. Set in Netlify dashboard or CLI:
+   ```bash
+   npx netlify env:set API_KEY "secret_value"
+   npx netlify env:set NODE_ENV "production"
+   ```
+3. Access in code: `process.env.API_KEY`
+4. Deploy: `npx netlify deploy --prod`
+
+## Scenario 7: Custom Domain Setup
+
+**Context**: User wants to use a custom domain.
+
+**Steps**:
+1. Deploy site first: `npx netlify deploy --prod`
+2. Add domain via dashboard or CLI:
+   ```bash
+   npx netlify open:admin
+   # Navigate to Domain settings
+   ```
+3. Update DNS records as instructed by Netlify
+4. Wait for DNS propagation (can take up to 48 hours)
+
+## Best Practices
+
+### 1. Always Preview First
+
+```bash
+# Deploy preview
+npx netlify deploy
+
+# Test thoroughly
+# Then deploy to production
+npx netlify deploy --prod
+```
+
+### 2. Use netlify.toml for Consistency
+
+Create a `netlify.toml` file in your repo root:
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+
+[[redirects]]
+  from = "/*"
+  to = "/index.html"
+  status = 200
+```
+
+This ensures consistent builds across all deployments.
+
+### 3. Framework Detection
+
+Let Netlify auto-detect when possible. Only specify build settings if:
+- Netlify can't detect your framework
+- You need custom build commands
+- Your project has a non-standard structure
+
+### 4. Dependency Installation
+
+Always ensure dependencies are installed before deploying:
+
+```bash
+npm install  # or yarn install, pnpm install
+npx netlify deploy
+```
+
+### 5. Build Locally First
+
+Test builds locally before deploying:
+
+```bash
+npm run build
+# Check that build output exists
+
+npx netlify deploy --dir=dist
+```
+
+### 6. Use Deploy Messages
+
+Add context to deployments:
+
+```bash
+npx netlify deploy --prod --message="Fix login bug"
+```
+
+## Error Recovery Patterns
+
+### "Publish directory not found"
+
+**Cause**: Build command didn't create expected output directory.
+
+**Fix**:
+1. Run build locally: `npm run build`
+2. Check output directory name
+3. Update netlify.toml or CLI prompts with correct path
+
+### "Command failed with exit code 1"
+
+**Cause**: Build command failed.
+
+**Fix**:
+1. Check build logs for specific error
+2. Run build locally to reproduce: `npm run build`
+3. Fix the build error
+4. Deploy again
+
+### "Not logged in"
+
+**Cause**: Authentication token expired or missing.
+
+**Fix**:
+```bash
+npx netlify logout
+npx netlify login
+```
+
+### "No site linked"
+
+**Cause**: Project not connected to a Netlify site.
+
+**Fix**:
+```bash
+# Try linking to existing site
+npx netlify link
+
+# Or create new site
+npx netlify init
+```
+
+## Performance Tips
+
+1. **Enable processing** in netlify.toml for auto-optimization:
+   ```toml
+   [build.processing.css]
+     bundle = true
+     minify = true
+   ```
+
+2. **Use caching headers** for static assets:
+   ```toml
+   [[headers]]
+     for = "/assets/*"
+     [headers.values]
+       Cache-Control = "public, max-age=31536000, immutable"
+   ```
+
+3. **Optimize images** before deploying or use Netlify Image CDN
+
+4. **Use Netlify Functions** for serverless backend (avoid external API calls when possible)
+
+## Resources
+
+- Netlify CLI Documentation: https://docs.netlify.com/cli/get-started/
+- Framework Integration Guides: https://docs.netlify.com/frameworks/
+- Build Configuration: https://docs.netlify.com/configure-builds/

package/dist/registry/skills/openai-netlify-deploy/upstream/references/netlify-toml.md

@@ -0,0 +1,259 @@
+# netlify.toml Configuration Reference
+
+Configuration file for Netlify builds and deployments.
+
+## Basic Structure
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+```
+
+## Build Settings
+
+### Common Configuration
+
+```toml
+[build]
+  # Command to build your site
+  command = "npm run build"
+
+  # Directory to publish (relative to repo root)
+  publish = "dist"
+
+  # Functions directory
+  functions = "netlify/functions"
+
+  # Base directory (if not repo root)
+  base = "packages/frontend"
+
+  # Ignore builds for specific conditions
+  ignore = "git diff --quiet HEAD^ HEAD package.json"
+```
+
+## Environment Variables
+
+```toml
+[build.environment]
+  NODE_VERSION = "18"
+  NPM_FLAGS = "--prefix=/dev/null"
+
+[context.production.environment]
+  NODE_ENV = "production"
+```
+
+## Framework Detection
+
+Netlify auto-detects frameworks, but you can override:
+
+### Next.js
+
+```toml
+[build]
+  command = "npm run build"
+  publish = ".next"
+```
+
+### React (Vite)
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+```
+
+### Vue
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+```
+
+### Astro
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+```
+
+### SvelteKit
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "build"
+```
+
+## Redirects and Rewrites
+
+```toml
+[[redirects]]
+  from = "/old-path"
+  to = "/new-path"
+  status = 301
+
+[[redirects]]
+  from = "/api/*"
+  to = "https://api.example.com/:splat"
+  status = 200
+
+# SPA fallback (for client-side routing)
+[[redirects]]
+  from = "/*"
+  to = "/index.html"
+  status = 200
+```
+
+## Headers
+
+```toml
+[[headers]]
+  for = "/*"
+  [headers.values]
+    X-Frame-Options = "DENY"
+    X-XSS-Protection = "1; mode=block"
+    Content-Security-Policy = "default-src 'self'"
+
+[[headers]]
+  for = "/assets/*"
+  [headers.values]
+    Cache-Control = "public, max-age=31536000, immutable"
+```
+
+## Context-Specific Configuration
+
+Deploy different settings per context:
+
+```toml
+# Production
+[context.production]
+  command = "npm run build:prod"
+  [context.production.environment]
+    NODE_ENV = "production"
+
+# Deploy previews
+[context.deploy-preview]
+  command = "npm run build:preview"
+
+# Branch deploys
+[context.branch-deploy]
+  command = "npm run build:staging"
+
+# Specific branch
+[context.staging]
+  command = "npm run build:staging"
+```
+
+## Functions Configuration
+
+```toml
+[functions]
+  directory = "netlify/functions"
+  node_bundler = "esbuild"
+
+[[functions]]
+  path = "/api/*"
+  function = "api"
+```
+
+## Build Plugins
+
+```toml
+[[plugins]]
+  package = "@netlify/plugin-lighthouse"
+
+  [plugins.inputs]
+    output_path = "reports/lighthouse.html"
+
+[[plugins]]
+  package = "netlify-plugin-submit-sitemap"
+
+  [plugins.inputs]
+    baseUrl = "https://example.com"
+    sitemapPath = "/sitemap.xml"
+```
+
+## Edge Functions
+
+```toml
+[[edge_functions]]
+  function = "geolocation"
+  path = "/api/location"
+```
+
+## Processing
+
+```toml
+[build.processing]
+  skip_processing = false
+
+[build.processing.css]
+  bundle = true
+  minify = true
+
+[build.processing.js]
+  bundle = true
+  minify = true
+
+[build.processing.html]
+  pretty_urls = true
+
+[build.processing.images]
+  compress = true
+```
+
+## Common Patterns
+
+### Single Page Application (SPA)
+
+```toml
+[build]
+  command = "npm run build"
+  publish = "dist"
+
+[[redirects]]
+  from = "/*"
+  to = "/index.html"
+  status = 200
+```
+
+### Monorepo with Base Directory
+
+```toml
+[build]
+  base = "packages/web"
+  command = "npm run build"
+  publish = "dist"
+```
+
+### Multiple Redirects with Country-Based Routing
+
+```toml
+[[redirects]]
+  from = "/"
+  to = "/uk"
+  status = 302
+  conditions = {Country = ["GB"]}
+
+[[redirects]]
+  from = "/"
+  to = "/us"
+  status = 302
+  conditions = {Country = ["US"]}
+```
+
+## Validation
+
+Validate your netlify.toml:
+
+```bash
+npx netlify build --dry
+```
+
+## Resources
+
+- Full configuration reference: https://docs.netlify.com/configure-builds/file-based-configuration/
+- Framework-specific guides: https://docs.netlify.com/frameworks/

package/dist/registry/skills/openai-notion-knowledge-capture/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: openai-notion-knowledge-capture
+description: "Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking. (Imported from openai upstream skills)"
+version: "1.0.0"
+tags: ["openai", "upstream", "imported"]
+kind: knowledge
+risk: low
+availability: advanced
+docs:
+  source: "https://github.com/openai/skills/tree/main/skills/.curated/notion-knowledge-capture"
+---
+
+# openai-notion-knowledge-capture
+
+Imported upstream skill.
+
+- Provider source: https://github.com/openai/skills/tree/main/skills/.curated/notion-knowledge-capture
+- Original skill name: notion-knowledge-capture
+
+## Upstream Content
+
+# Knowledge Capture
+
+Convert conversations and notes into structured, linkable Notion pages for easy reuse.
+
+## Quick start
+1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
+2) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation).
+3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update/link).
+4) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners.
+5) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves.
+
+## Workflow
+### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
+1. Add the Notion MCP:
+   - `codex mcp add notion --url https://mcp.notion.com/mcp`
+2. Enable remote MCP client:
+   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
+3. Log in with OAuth:
+   - `codex mcp login notion`
+
+After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
+
+### 1) Define the capture
+- Ask purpose, audience, freshness, and whether this is new or an update.
+- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
+
+### 2) Locate destination
+- Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).
+- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
+
+### 3) Extract and structure
+- Extract facts, decisions, actions, and rationale from the conversation.
+- For decisions, record alternatives, rationale, and outcomes.
+- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
+- For FAQs, phrase as Q&A with concise answers and links to deeper docs.
+
+### 4) Create/update in Notion
+- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).
+- Use templates in `reference/` to structure content (section headers, checklists).
+- If updating an existing page, fetch then edit via `Notion:notion-update-page`.
+
+### 5) Link and surface
+- Add relations/backlinks to hub pages, related specs/docs, and teams.
+- Add a short summary/changelog for future readers.
+- If follow-up tasks exist, create tasks in the relevant database and link them.
+
+## References and examples
+- `reference/` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).
+- `examples/` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).

package/dist/registry/skills/openai-notion-knowledge-capture/upstream/LICENSE.txt

@@ -0,0 +1,7 @@
+Copyright 2025 Notion Labs, Inc.
+
+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/dist/registry/skills/openai-notion-knowledge-capture/upstream/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: notion-knowledge-capture
+description: Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
+metadata:
+  short-description: Capture conversations into structured Notion pages
+---
+
+# Knowledge Capture
+
+Convert conversations and notes into structured, linkable Notion pages for easy reuse.
+
+## Quick start
+1) Clarify what to capture (decision, how-to, FAQ, learning, documentation) and target audience.
+2) Identify the right database/template in `reference/` (team wiki, how-to, FAQ, decision log, learning, documentation).
+3) Pull any prior context from Notion with `Notion:notion-search` → `Notion:notion-fetch` (existing pages to update/link).
+4) Draft the page with `Notion:notion-create-pages` using the database’s schema; include summary, context, source links, and tags/owners.
+5) Link from hub pages and related records; update status/owners with `Notion:notion-update-page` as the source evolves.
+
+## Workflow
+### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
+1. Add the Notion MCP:
+   - `codex mcp add notion --url https://mcp.notion.com/mcp`
+2. Enable remote MCP client:
+   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
+3. Log in with OAuth:
+   - `codex mcp login notion`
+
+After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.
+
+### 1) Define the capture
+- Ask purpose, audience, freshness, and whether this is new or an update.
+- Determine content type: decision, how-to, FAQ, concept/wiki entry, learning/note, documentation page.
+
+### 2) Locate destination
+- Pick the correct database using `reference/*-database.md` guides; confirm required properties (title, tags, owner, status, date, relations).
+- If multiple candidate databases, ask the user which to use; otherwise, create in the primary wiki/documentation DB.
+
+### 3) Extract and structure
+- Extract facts, decisions, actions, and rationale from the conversation.
+- For decisions, record alternatives, rationale, and outcomes.
+- For how-tos/docs, capture steps, pre-reqs, links to assets/code, and edge cases.
+- For FAQs, phrase as Q&A with concise answers and links to deeper docs.
+
+### 4) Create/update in Notion
+- Use `Notion:notion-create-pages` with the correct `data_source_id`; set properties (title, tags, owner, status, dates, relations).
+- Use templates in `reference/` to structure content (section headers, checklists).
+- If updating an existing page, fetch then edit via `Notion:notion-update-page`.
+
+### 5) Link and surface
+- Add relations/backlinks to hub pages, related specs/docs, and teams.
+- Add a short summary/changelog for future readers.
+- If follow-up tasks exist, create tasks in the relevant database and link them.
+
+## References and examples
+- `reference/` — database schemas and templates (e.g., `team-wiki-database.md`, `how-to-guide-database.md`, `faq-database.md`, `decision-log-database.md`, `documentation-database.md`, `learning-database.md`, `database-best-practices.md`).
+- `examples/` — capture patterns in practice (e.g., `decision-capture.md`, `how-to-guide.md`, `conversation-to-faq.md`).

package/dist/registry/skills/openai-notion-knowledge-capture/upstream/agents/openai.yaml

@@ -0,0 +1,14 @@
+interface:
+  display_name: "Notion Knowledge Capture"
+  short_description: "Capture conversations into structured Notion pages"
+  icon_small: "./assets/notion-small.svg"
+  icon_large: "./assets/notion.png"
+  default_prompt: "Capture this conversation into structured Notion pages with decisions, action items, and owners when known."
+
+dependencies:
+  tools:
+    - type: "mcp"
+      value: "notion"
+      description: "Notion MCP server"
+      transport: "streamable_http"
+      url: "https://mcp.notion.com/mcp"