@ngxtm/devkit 3.7.0 → 3.9.0

package/merged-commands/atlassian-mcp.md

@@ -0,0 +1,100 @@
+---
+name: atlassian-mcp
+description: Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.
+triggers:
+  - Jira
+  - Confluence
+  - Atlassian
+  - MCP
+  - tickets
+  - issues
+  - wiki
+  - JQL
+  - CQL
+  - sprint
+  - backlog
+  - project management
+role: expert
+scope: implementation
+output-format: code
+---
+
+# Atlassian MCP Expert
+
+Senior integration specialist with deep expertise in connecting Jira, Confluence, and other Atlassian tools to AI systems via Model Context Protocol (MCP).
+
+## Role Definition
+
+You are an expert in Atlassian MCP integration with mastery of both official and open-source MCP servers, JQL/CQL query languages, OAuth 2.0 authentication, and production deployment patterns. You build robust workflows that automate issue triage, documentation sync, sprint planning, and cross-tool integration while respecting permissions and maintaining security.
+
+## When to Use This Skill
+
+- Querying Jira issues with JQL filters
+- Searching or creating Confluence pages
+- Automating sprint workflows and backlog management
+- Setting up MCP server authentication (OAuth/API tokens)
+- Syncing meeting notes to Jira tickets
+- Generating documentation from issue data
+- Debugging Atlassian API integration issues
+- Choosing between official vs open-source MCP servers
+
+## Core Workflow
+
+1. **Select server** - Choose official cloud, open-source, or self-hosted MCP server
+2. **Authenticate** - Configure OAuth 2.1, API tokens, or PAT credentials
+3. **Design queries** - Write JQL for Jira, CQL for Confluence, test filters
+4. **Implement workflow** - Build tool calls, handle pagination, error recovery
+5. **Deploy** - Configure IDE integration, test permissions, monitor rate limits
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Server Setup | `references/mcp-server-setup.md` | Installation, choosing servers, configuration |
+| Jira Operations | `references/jira-queries.md` | JQL syntax, issue CRUD, sprints, boards |
+| Confluence Ops | `references/confluence-operations.md` | CQL search, page creation, spaces, comments |
+| Authentication | `references/authentication-patterns.md` | OAuth 2.0, API tokens, permission scopes |
+| Common Workflows | `references/common-workflows.md` | Issue triage, doc sync, sprint automation |
+
+## Constraints
+
+### MUST DO
+- Respect user permissions and workspace access controls
+- Validate JQL/CQL queries before execution
+- Handle rate limits with exponential backoff
+- Use pagination for large result sets (50-100 items per page)
+- Implement error recovery for network failures
+- Log API calls for debugging and audit trails
+- Test with read-only operations first
+- Document required permission scopes
+
+### MUST NOT DO
+- Hardcode API tokens or OAuth secrets in code
+- Ignore rate limit headers from Atlassian APIs
+- Create issues without validating required fields
+- Skip input sanitization on user-provided query strings
+- Deploy without testing permission boundaries
+- Update production data without confirmation prompts
+- Mix different authentication methods in same session
+- Expose sensitive issue data in logs or error messages
+
+## Output Templates
+
+When implementing Atlassian MCP features, provide:
+1. MCP server configuration (JSON/environment vars)
+2. Query examples (JQL/CQL with explanations)
+3. Tool call implementation with error handling
+4. Authentication setup instructions
+5. Brief explanation of permission requirements
+
+## Knowledge Reference
+
+Atlassian MCP Server (official), mcp-atlassian (sooperset), atlassian-mcp (xuanxt), JQL (Jira Query Language), CQL (Confluence Query Language), OAuth 2.1, API tokens, Personal Access Tokens (PAT), Model Context Protocol, JSON-RPC 2.0, rate limiting, pagination, permission scopes, Jira REST API, Confluence REST API
+
+## Related Skills
+
+- **MCP Developer** - Building custom MCP servers and protocol compliance
+- **API Designer** - REST API integration patterns and error handling
+- **Security Reviewer** - OAuth security audits and token management

package/merged-commands/attack-tree-construction.md

@@ -0,0 +1,38 @@
+---
+name: attack-tree-construction
+description: Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
+---
+
+# Attack Tree Construction
+
+Systematic attack path visualization and analysis.
+
+## Use this skill when
+
+- Visualizing complex attack scenarios
+- Identifying defense gaps and priorities
+- Communicating risks to stakeholders
+- Planning defensive investments or test scopes
+
+## Do not use this skill when
+
+- You lack authorization or a defined scope to model the system
+- The task is a general risk review without attack-path modeling
+- The request is unrelated to security assessment or design
+
+## Instructions
+
+- Confirm scope, assets, and the attacker goal for the root node.
+- Decompose into sub-goals with AND/OR structure.
+- Annotate leaves with cost, skill, time, and detectability.
+- Map mitigations per branch and prioritize high-impact paths.
+- If detailed templates are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Share attack trees only with authorized stakeholders.
+- Avoid including sensitive exploit details unless required.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns, templates, and examples.

package/merged-commands/auth-implementation-patterns.md

@@ -0,0 +1,39 @@
+---
+name: auth-implementation-patterns
+description: Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
+---
+
+# Authentication & Authorization Implementation Patterns
+
+Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.
+
+## Use this skill when
+
+- Implementing user authentication systems
+- Securing REST or GraphQL APIs
+- Adding OAuth2/social login or SSO
+- Designing session management or RBAC
+- Debugging authentication or authorization issues
+
+## Do not use this skill when
+
+- You only need UI copy or login page styling
+- The task is infrastructure-only without identity concerns
+- You cannot change auth policies or credential storage
+
+## Instructions
+
+- Define users, tenants, flows, and threat model constraints.
+- Choose auth strategy (session, JWT, OIDC) and token lifecycle.
+- Design authorization model and policy enforcement points.
+- Plan secrets storage, rotation, logging, and audit requirements.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Safety
+
+- Never log secrets, tokens, or credentials.
+- Enforce least privilege and secure storage for keys.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.

package/merged-commands/automate-whatsapp.md

@@ -0,0 +1,257 @@
+---
+name: automate-whatsapp
+description: "Build WhatsApp automations with Kapso workflows: configure WhatsApp triggers, edit workflow graphs, manage executions, deploy functions, and use databases/integrations for state. Use when automating WhatsApp conversations and event handling."
+source: "https://github.com/gokapso/agent-skills/tree/master/skills/automate-whatsapp"
+risk: safe
+---
+
+# Automate WhatsApp
+
+## When to use
+
+Use this skill to build and run WhatsApp automations: workflow CRUD, graph edits, triggers, executions, function management, app integrations, and D1 database operations.
+
+## Setup
+
+Env vars:
+- `KAPSO_API_BASE_URL` (host only, no `/platform/v1`)
+- `KAPSO_API_KEY`
+
+## How to
+
+### Edit a workflow graph
+
+1. Fetch graph: `node scripts/get-graph.js <workflow_id>` (note the `lock_version`)
+2. Edit the JSON (see graph rules below)
+3. Validate: `node scripts/validate-graph.js --definition-file <path>`
+4. Update: `node scripts/update-graph.js <workflow_id> --expected-lock-version <n> --definition-file <path>`
+5. Re-fetch to confirm
+
+For small edits, use `edit-graph.js` with `--old-file` and `--new-file` instead.
+
+If you get a lock_version conflict: re-fetch, re-apply changes, retry with new lock_version.
+
+### Manage triggers
+
+1. List: `node scripts/list-triggers.js <workflow_id>`
+2. Create: `node scripts/create-trigger.js <workflow_id> --trigger-type <type> --phone-number-id <id>`
+3. Toggle: `node scripts/update-trigger.js --trigger-id <id> --active true|false`
+4. Delete: `node scripts/delete-trigger.js --trigger-id <id>`
+
+For inbound_message triggers, first run `node scripts/list-whatsapp-phone-numbers.js` to get `phone_number_id`.
+
+### Debug executions
+
+1. List: `node scripts/list-executions.js <workflow_id>`
+2. Inspect: `node scripts/get-execution.js <execution-id>`
+3. Get value: `node scripts/get-context-value.js <execution-id> --variable-path vars.foo`
+4. Events: `node scripts/list-execution-events.js <execution-id>`
+
+### Create and deploy a function
+
+1. Write code with handler signature (see function rules below)
+2. Create: `node scripts/create-function.js --name <name> --code-file <path>`
+3. Deploy: `node scripts/deploy-function.js --function-id <id>`
+4. Verify: `node scripts/get-function.js --function-id <id>`
+
+### Set up agent node with app integrations
+
+1. Find model: `node scripts/list-provider-models.js`
+2. Find account: `node scripts/list-accounts.js --app-slug <slug>` (use `pipedream_account_id`)
+3. Find action: `node scripts/search-actions.js --query <word> --app-slug <slug>` (action_id = key)
+4. Create integration: `node scripts/create-integration.js --action-id <id> --app-slug <slug> --account-id <id> --configured-props <json>`
+5. Add tools to agent node via `flow_agent_app_integration_tools`
+
+### Database CRUD
+
+1. List tables: `node scripts/list-tables.js`
+2. Query: `node scripts/query-rows.js --table <name> --filters <json>`
+3. Create/update/delete with row scripts
+
+## Graph rules
+
+- Exactly one start node with `id` = `start`
+- Never change existing node IDs
+- Use `{node_type}_{timestamp_ms}` for new node IDs
+- Non-decide nodes have 0 or 1 outgoing `next` edge
+- Decide edge labels must match `conditions[].label`
+- Edge keys are `source`/`target`/`label` (not `from`/`to`)
+
+For full schema details, see `references/graph-contract.md`.
+
+## Function rules
+
+```js
+async function handler(request, env) {
+  // Parse input
+  const body = await request.json();
+  // Use env.KV and env.DB as needed
+  return new Response(JSON.stringify({ result: "ok" }));
+}
+```
+
+- Do NOT use `export`, `export default`, or arrow functions
+- Return a `Response` object
+
+## Execution context
+
+Always use this structure:
+- `vars` - user-defined variables
+- `system` - system variables
+- `context` - channel data
+- `metadata` - request metadata
+
+## Scripts
+
+### Workflows
+
+| Script | Purpose |
+|--------|---------|
+| `list-workflows.js` | List workflows (metadata only) |
+| `get-workflow.js` | Get workflow metadata |
+| `create-workflow.js` | Create a workflow |
+| `update-workflow-settings.js` | Update workflow settings |
+
+### Graph
+
+| Script | Purpose |
+|--------|---------|
+| `get-graph.js` | Get workflow graph + lock_version |
+| `edit-graph.js` | Patch graph via string replacement |
+| `update-graph.js` | Replace entire graph |
+| `validate-graph.js` | Validate graph structure locally |
+
+### Triggers
+
+| Script | Purpose |
+|--------|---------|
+| `list-triggers.js` | List triggers for a workflow |
+| `create-trigger.js` | Create a trigger |
+| `update-trigger.js` | Enable/disable a trigger |
+| `delete-trigger.js` | Delete a trigger |
+| `list-whatsapp-phone-numbers.js` | List phone numbers for trigger setup |
+
+### Executions
+
+| Script | Purpose |
+|--------|---------|
+| `list-executions.js` | List executions |
+| `get-execution.js` | Get execution details |
+| `get-context-value.js` | Read value from execution context |
+| `update-execution-status.js` | Force execution state |
+| `resume-execution.js` | Resume waiting execution |
+| `list-execution-events.js` | List execution events |
+
+### Functions
+
+| Script | Purpose |
+|--------|---------|
+| `list-functions.js` | List project functions |
+| `get-function.js` | Get function details + code |
+| `create-function.js` | Create a function |
+| `update-function.js` | Update function code |
+| `deploy-function.js` | Deploy function to runtime |
+| `invoke-function.js` | Invoke function with payload |
+| `list-function-invocations.js` | List function invocations |
+
+### App integrations
+
+| Script | Purpose |
+|--------|---------|
+| `list-apps.js` | Search integration apps |
+| `search-actions.js` | Search actions (action_id = key) |
+| `get-action-schema.js` | Get action JSON schema |
+| `list-accounts.js` | List connected accounts |
+| `create-connect-token.js` | Create OAuth connect link |
+| `configure-prop.js` | Resolve remote_options for a prop |
+| `reload-props.js` | Reload dynamic props |
+| `list-integrations.js` | List saved integrations |
+| `create-integration.js` | Create an integration |
+| `update-integration.js` | Update an integration |
+| `delete-integration.js` | Delete an integration |
+
+### Databases
+
+| Script | Purpose |
+|--------|---------|
+| `list-tables.js` | List D1 tables |
+| `get-table.js` | Get table schema + sample rows |
+| `query-rows.js` | Query rows with filters |
+| `create-row.js` | Create a row |
+| `update-row.js` | Update rows |
+| `upsert-row.js` | Upsert a row |
+| `delete-row.js` | Delete rows |
+
+### OpenAPI
+
+| Script | Purpose |
+|--------|---------|
+| `openapi-explore.mjs` | Explore OpenAPI (search/op/schema/where) |
+
+Install deps (once):
+```bash
+npm i
+```
+
+Examples:
+```bash
+node scripts/openapi-explore.mjs --spec workflows search "variables"
+node scripts/openapi-explore.mjs --spec workflows op getWorkflowVariables
+node scripts/openapi-explore.mjs --spec platform op queryDatabaseRows
+```
+
+## Notes
+
+- Prefer file paths over inline JSON (`--definition-file`, `--code-file`)
+- `action_id` is the same as `key` from `search-actions`
+- `--account-id` uses `pipedream_account_id` from `list-accounts`
+- Variable CRUD (`variables-set.js`, `variables-delete.js`) is blocked - Platform API doesn't support it
+- Raw SQL execution is not supported via Platform API
+
+## References
+
+Read before editing:
+- [references/graph-contract.md](references/graph-contract.md) - Graph schema, computed vs editable fields, lock_version
+- [references/node-types.md](references/node-types.md) - Node types and config shapes
+- [references/workflow-overview.md](references/workflow-overview.md) - Execution flow and states
+
+Other references:
+- [references/execution-context.md](references/execution-context.md) - Context structure and variable substitution
+- [references/triggers.md](references/triggers.md) - Trigger types and setup
+- [references/app-integrations.md](references/app-integrations.md) - App integration and variable_definitions
+- [references/functions-reference.md](references/functions-reference.md) - Function management
+- [references/functions-payloads.md](references/functions-payloads.md) - Payload shapes for functions
+- [references/databases-reference.md](references/databases-reference.md) - Database operations
+
+## Assets
+
+| File | Description |
+|------|-------------|
+| `workflow-linear.json` | Minimal linear workflow |
+| `workflow-decision.json` | Minimal branching workflow |
+| `workflow-agent-simple.json` | Minimal agent workflow |
+| `workflow-customer-support-intake-agent.json` | Customer support intake |
+| `workflow-interactive-buttons-decide-function.json` | Interactive buttons + decide (function) |
+| `workflow-interactive-buttons-decide-ai.json` | Interactive buttons + decide (AI) |
+| `workflow-api-template-wait-agent.json` | API trigger + template + agent |
+| `function-decide-route-interactive-buttons.json` | Function for button routing |
+| `agent-app-integration-example.json` | Agent node with app integrations |
+
+## Related skills
+
+- `integrate-whatsapp` - Onboarding, webhooks, messaging, templates, flows
+- `observe-whatsapp` - Debugging, logs, health checks
+
+<!-- FILEMAP:BEGIN -->
+```text
+[automate-whatsapp file map]|root: .
+|.:{package.json,SKILL.md}
+|assets:{agent-app-integration-example.json,databases-example.json,function-decide-route-interactive-buttons.json,functions-example.json,workflow-agent-simple.json,workflow-api-template-wait-agent.json,workflow-customer-support-intake-agent.json,workflow-decision.json,workflow-interactive-buttons-decide-ai.json,workflow-interactive-buttons-decide-function.json,workflow-linear.json}
+|references:{app-integrations.md,databases-reference.md,execution-context.md,function-contracts.md,functions-payloads.md,functions-reference.md,graph-contract.md,node-types.md,triggers.md,workflow-overview.md,workflow-reference.md}
+|scripts:{configure-prop.js,create-connect-token.js,create-function.js,create-integration.js,create-row.js,create-trigger.js,create-workflow.js,delete-integration.js,delete-row.js,delete-trigger.js,deploy-function.js,edit-graph.js,get-action-schema.js,get-context-value.js,get-execution-event.js,get-execution.js,get-function.js,get-graph.js,get-table.js,get-workflow.js,invoke-function.js,list-accounts.js,list-apps.js,list-execution-events.js,list-executions.js,list-function-invocations.js,list-functions.js,list-integrations.js,list-provider-models.js,list-tables.js,list-triggers.js,list-whatsapp-phone-numbers.js,list-workflows.js,openapi-explore.mjs,query-rows.js,reload-props.js,resume-execution.js,search-actions.js,update-execution-status.js,update-function.js,update-graph.js,update-integration.js,update-row.js,update-trigger.js,update-workflow-settings.js,upsert-row.js,validate-graph.js,variables-delete.js,variables-list.js,variables-set.js}
+|scripts/lib/databases:{args.js,filters.js,kapso-api.js}
+|scripts/lib/functions:{args.js,kapso-api.js}
+|scripts/lib/workflows:{args.js,kapso-api.js,result.js}
+```
+<!-- FILEMAP:END -->
+