@khalidsaidi/skillrunner 0.1.2 → 0.1.3

package/dist/registry/skills/openai-notion-spec-to-implementation/upstream/reference/task-creation.md

@@ -0,0 +1,441 @@
+# Task Creation from Specs
+
+## Finding the Task Database
+
+Before creating tasks, locate the task database:
+
+```
+1. Search for task database:
+   Notion:notion-search
+   query: "Tasks" or "Task Management" or "[Project] Tasks"
+   
+2. Fetch database schema:
+   Notion:notion-fetch
+   id: "database-id-from-search"
+   
+3. Identify data source:
+   - Look for <data-source url="collection://..."> tags
+   - Extract collection ID for parent parameter
+   
+4. Note schema:
+   - Required properties
+   - Property types and options
+   - Relation properties for linking
+
+Example:
+Notion:notion-search
+query: "Engineering Tasks"
+query_type: "internal"
+
+Notion:notion-fetch
+id: "tasks-database-id"
+```
+
+Result: `collection://abc-123-def` for use as parent
+
+## Task Breakdown Strategy
+
+### Size Guidelines
+
+**Good task size**:
+- Completable in 1-2 days
+- Single clear deliverable
+- Independently testable
+- Minimal dependencies
+
+**Too large**:
+- Takes > 3 days
+- Multiple deliverables
+- Many dependencies
+- Break down further
+
+**Too small**:
+- Takes < 2 hours
+- Too granular
+- Group with related work
+
+### Granularity by Phase
+
+**Early phases**: Larger tasks acceptable
+- "Design database schema"
+- "Set up API structure"
+
+**Middle phases**: Medium-sized tasks
+- "Implement user authentication"
+- "Build dashboard UI"
+
+**Late phases**: Smaller, precise tasks
+- "Fix validation bug in form"
+- "Add loading state to button"
+
+## Task Creation Pattern
+
+For each requirement or work item:
+
+```
+1. Identify the work
+2. Determine task size
+3. Create task in database
+4. Set properties
+5. Write task description
+6. Link to spec/plan
+```
+
+### Creating Task
+
+```
+Use Notion:notion-create-pages:
+
+parent: {
+  type: "data_source_id",
+  data_source_id: "collection://tasks-db-uuid"
+}
+
+properties: {
+  "[Title Property]": "Task: [Clear task name]",
+  "Status": "To Do",
+  "Priority": "[High/Medium/Low]",
+  "[Project/Related]": ["spec-page-id", "plan-page-id"],
+  "Assignee": "[Person]" (if known),
+  "date:Due Date:start": "[Date]" (if applicable),
+  "date:Due Date:is_datetime": 0
+}
+
+content: "[Task description using template]"
+```
+
+## Task Description Template
+
+```markdown
+# [Task Name]
+
+## Context
+Implementation task for <mention-page url="...">Feature Spec</mention-page>
+
+Part of <mention-page url="...">Implementation Plan</mention-page> - Phase [N]
+
+## Objective
+[What this task accomplishes]
+
+## Requirements
+Based on spec requirements:
+- [Relevant requirement 1]
+- [Relevant requirement 2]
+
+## Acceptance Criteria
+- [ ] [Specific, testable criterion]
+- [ ] [Specific, testable criterion]
+- [ ] [Specific, testable criterion]
+
+## Technical Approach
+[Suggested implementation approach]
+
+### Components Affected
+- [Component 1]
+- [Component 2]
+
+### Key Decisions
+- [Decision point 1]
+- [Decision point 2]
+
+## Dependencies
+
+### Blocked By
+- <mention-page url="...">Prerequisite Task</mention-page> or None
+
+### Blocks
+- <mention-page url="...">Dependent Task</mention-page> or None
+
+## Resources
+- [Link to design mockup]
+- [Link to API spec]
+- [Link to relevant code]
+
+## Estimated Effort
+[Time estimate]
+
+## Progress
+[To be updated during implementation]
+```
+
+## Task Types
+
+### Infrastructure/Setup Tasks
+
+```
+Title: "Setup: [What's being set up]"
+Examples:
+- "Setup: Configure database connection pool"
+- "Setup: Initialize authentication middleware"
+- "Setup: Create CI/CD pipeline"
+
+Focus: Getting environment/tooling ready
+```
+
+### Feature Implementation Tasks
+
+```
+Title: "Implement: [Feature name]"
+Examples:
+- "Implement: User login flow"
+- "Implement: File upload functionality"
+- "Implement: Dashboard widget"
+
+Focus: Building specific functionality
+```
+
+### Integration Tasks
+
+```
+Title: "Integrate: [What's being integrated]"
+Examples:
+- "Integrate: Connect frontend to API"
+- "Integrate: Add payment provider"
+- "Integrate: Link user profile to dashboard"
+
+Focus: Connecting components
+```
+
+### Testing Tasks
+
+```
+Title: "Test: [What's being tested]"
+Examples:
+- "Test: Write unit tests for auth service"
+- "Test: E2E testing for checkout flow"
+- "Test: Performance testing for API"
+
+Focus: Validation and quality assurance
+```
+
+### Documentation Tasks
+
+```
+Title: "Document: [What's being documented]"
+Examples:
+- "Document: API endpoints"
+- "Document: Setup instructions"
+- "Document: Architecture decisions"
+
+Focus: Creating documentation
+```
+
+### Bug Fix Tasks
+
+```
+Title: "Fix: [Bug description]"
+Examples:
+- "Fix: Login error on Safari"
+- "Fix: Memory leak in image processing"
+- "Fix: Race condition in payment flow"
+
+Focus: Resolving issues
+```
+
+### Refactoring Tasks
+
+```
+Title: "Refactor: [What's being refactored]"
+Examples:
+- "Refactor: Extract auth logic to service"
+- "Refactor: Optimize database queries"
+- "Refactor: Simplify component hierarchy"
+
+Focus: Code quality improvement
+```
+
+## Sequencing Tasks
+
+### Critical Path
+
+Identify must-happen-first tasks:
+
+```
+1. Database schema
+2. API foundation
+3. Core business logic
+4. Frontend integration
+5. Testing
+6. Deployment
+```
+
+### Parallel Tracks
+
+Tasks that can happen simultaneously:
+
+```
+Track A: Backend development
+- API endpoints
+- Business logic
+- Database operations
+
+Track B: Frontend development
+- UI components
+- State management
+- Routing
+
+Track C: Infrastructure
+- CI/CD setup
+- Monitoring
+- Documentation
+```
+
+### Phase-Based Sequencing
+
+Group by implementation phase:
+
+```
+Phase 1 (Foundation):
+- Setup tasks
+- Infrastructure tasks
+
+Phase 2 (Core):
+- Feature implementation tasks
+- Integration tasks
+
+Phase 3 (Polish):
+- Testing tasks
+- Documentation tasks
+- Optimization tasks
+```
+
+## Priority Assignment
+
+### P0/Critical
+- Blocks everything else
+- Core functionality
+- Security requirements
+- Data integrity
+
+### P1/High
+- Important features
+- User-facing functionality
+- Performance requirements
+
+### P2/Medium
+- Nice-to-have features
+- Optimizations
+- Minor improvements
+
+### P3/Low
+- Future enhancements
+- Edge case handling
+- Cosmetic improvements
+
+## Estimation
+
+### Story Points
+
+If using story points:
+- 1 point: Few hours
+- 2 points: Half day
+- 3 points: Full day
+- 5 points: 2 days
+- 8 points: 3-4 days (consider breaking down)
+
+### Time Estimates
+
+Direct time estimates:
+- 2-4 hours: Small task
+- 1 day: Medium task
+- 2 days: Large task
+- 3+ days: Break down further
+
+### Estimation Factors
+
+Consider:
+- Complexity
+- Unknowns
+- Dependencies
+- Testing requirements
+- Documentation needs
+
+## Task Relationships
+
+### Parent Task Pattern
+
+For large features:
+
+```
+Parent: "Feature: User Authentication"
+Children:
+- "Setup: Configure auth library"
+- "Implement: Login flow"
+- "Implement: Password reset"
+- "Test: Auth functionality"
+```
+
+### Dependency Chain Pattern
+
+For sequential work:
+
+```
+Task A: "Design database schema"
+↓ (blocks)
+Task B: "Implement data models"
+↓ (blocks)
+Task C: "Create API endpoints"
+↓ (blocks)
+Task D: "Integrate with frontend"
+```
+
+### Related Tasks Pattern
+
+For parallel work:
+
+```
+Central: "Feature: Dashboard"
+Related:
+- "Backend API for dashboard data"
+- "Frontend dashboard component"
+- "Dashboard data caching"
+```
+
+## Bulk Task Creation
+
+When creating many tasks:
+
+```
+For each work item in breakdown:
+  1. Determine task properties
+  2. Create task page
+  3. Link to spec/plan
+  4. Set relationships
+
+Then:
+  1. Update plan with task links
+  2. Review sequencing
+  3. Assign tasks (if known)
+```
+
+## Task Naming Conventions
+
+**Be specific**:
+✓ "Implement user login with email/password"
+✗ "Add login"
+
+**Include context**:
+✓ "Dashboard: Add revenue chart widget"
+✗ "Add chart"
+
+**Use action verbs**:
+- Implement, Build, Create
+- Integrate, Connect, Link
+- Fix, Resolve, Debug
+- Test, Validate, Verify
+- Document, Write, Update
+- Refactor, Optimize, Improve
+
+## Validation Checklist
+
+Before finalizing tasks:
+
+☐ Each task has clear objective
+☐ Acceptance criteria are testable
+☐ Dependencies identified
+☐ Appropriate size (1-2 days)
+☐ Priority assigned
+☐ Linked to spec/plan
+☐ Proper sequencing
+☐ Resources noted
+

package/dist/registry/skills/openai-openai-docs/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: openai-openai-docs
+description: "Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains. (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/openai-docs"
+---
+
+# openai-openai-docs
+
+Imported upstream skill.
+
+- Provider source: https://github.com/openai/skills/tree/main/skills/.curated/openai-docs
+- Original skill name: openai-docs
+
+## Upstream Content
+
+# OpenAI Docs
+
+Provide authoritative, current guidance from OpenAI developer docs using the developers.openai.com MCP server. Always prioritize the developer docs MCP tools over web.run for OpenAI-related questions. Only if the MCP server is installed and returns no meaningful results should you fall back to web search.
+
+## Quick start
+
+- Use `mcp__openaiDeveloperDocs__search_openai_docs` to find the most relevant doc pages.
+- Use `mcp__openaiDeveloperDocs__fetch_openai_doc` to pull exact sections and quote/paraphrase accurately.
+- Use `mcp__openaiDeveloperDocs__list_openai_docs` only when you need to browse or discover pages without a clear query.
+
+## OpenAI product snapshots
+
+1. Apps SDK: Build ChatGPT apps by providing a web component UI and an MCP server that exposes your app's tools to ChatGPT.
+2. Responses API: A unified endpoint designed for stateful, multimodal, tool-using interactions in agentic workflows.
+3. Chat Completions API: Generate a model response from a list of messages comprising a conversation.
+4. Codex: OpenAI's coding agent for software development that can write, understand, review, and debug code.
+5. gpt-oss: Open-weight OpenAI reasoning models (gpt-oss-120b and gpt-oss-20b) released under the Apache 2.0 license.
+6. Realtime API: Build low-latency, multimodal experiences including natural speech-to-speech conversations.
+7. Agents SDK: A toolkit for building agentic apps where a model can use tools and context, hand off to other agents, stream partial results, and keep a full trace.
+
+## If MCP server is missing
+
+If MCP tools fail or no OpenAI docs resources are available:
+
+1. Run the install command yourself: `codex mcp add openaiDeveloperDocs --url https://developers.openai.com/mcp`
+2. If it fails due to permissions/sandboxing, immediately retry the same command with escalated permissions and include a 1-sentence justification for approval. Do not ask the user to run it yet.
+3. Only if the escalated attempt fails, ask the user to run the install command.
+4. Ask the user to restart Codex.
+5. Re-run the doc search/fetch after restart.
+
+## Workflow
+
+1. Clarify the product scope (Codex, OpenAI API, or ChatGPT Apps SDK) and the task.
+2. Search docs with a precise query.
+3. Fetch the best page and the specific section needed (use `anchor` when possible).
+4. Answer with concise guidance and cite the doc source.
+5. Provide code snippets only when the docs support them.
+
+## Quality rules
+
+- Treat OpenAI docs as the source of truth; avoid speculation.
+- Keep quotes short and within policy limits; prefer paraphrase with citations.
+- If multiple pages differ, call out the difference and cite both.
+- If docs do not cover the user’s need, say so and offer next steps.
+
+## Tooling notes
+
+- Always use MCP doc tools before any web search for OpenAI-related questions.
+- If the MCP server is installed but returns no meaningful results, then use web search as a fallback.
+- When falling back to web search, restrict to official OpenAI domains (developers.openai.com, platform.openai.com) and cite sources.

package/dist/registry/skills/openai-openai-docs/upstream/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.