generate

Generate context-stocker plugins from wizard answers and .team-config.json files.

2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/iridon0920/context-stocker-forge --skill generate-iridon0920
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate
Source: https://github.com/iridon0920/context-stocker-forge/tree/main/skills/generate
Command: npx skills add https://github.com/iridon0920/context-stocker-forge --skill generate-iridon0920

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides B2B product teams through an interactive wizard to collect product, team, storage, and framework settings, then automates templating, validation, and packaging so teams do not need to manually assemble or configure context-stocker plugins.

Core Features & Use Cases

  • Interactive wizard: Step-by-step collection and validation of team name, product, command prefix, storage type, data sources, sales framework, and knowledge categories.
  • Template assembly & packaging: Computes derived variables, injects storage-specific adapters, renders templates with a Node.js engine, runs post-generation validation, and produces a .plugin ZIP with a compliant plugin.json.
  • Re-generation & migration: Supports re-generating from an existing .team-config.json and migrating storage/format versions by sampling and converting pages for Backlog Wiki or Obsidian Vault.
  • Use case: Quickly create a zendesk-context-stocker plugin configured for Backlog Wiki or an obsidian vault, complete with commands and skills for deal, knowledge, admin, doc, and log workflows.

Quick Start

Run the generate wizard and follow the prompts to produce a packaged .plugin file from your team and storage information.

Frequently Asked Questions about generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an Obsidian context-stocker plugin for my B2B product team?

To generate an Obsidian context-stocker plugin, run the interactive wizard to collect team, product, storage, and framework settings, then the engine validates inputs, renders templates, and packages a ready-to-deploy .plugin ZIP file.

Can I re-generate a context-stocker plugin from an existing .team-config.json file?

Yes, you can re-generate a context-stocker plugin from an existing .team-config.json file by loading the configuration to skip the wizard, recomputing derived template variables, and repackaging the updated .plugin ZIP.

How do I migrate context-stocker storage formats between Backlog Wiki and Obsidian Vault?

To migrate storage formats between Backlog Wiki and Obsidian Vault, the generator samples and converts existing pages, applies storage-specific adapters, and renders the correct templates to produce the migrated .plugin package.

What settings does the context-stocker plugin wizard collect for B2B product teams?

The wizard collects team name, product, command prefix, storage type, data sources, sales framework, and knowledge categories, validating each input against rules before template assembly.

Does the generated context-stocker plugin include built-in commands for deal and knowledge workflows?

Yes, the generated context-stocker plugin includes configured commands and skills for deal, knowledge, admin, doc, and log workflows based on your wizard inputs and selected storage adapters.

What happens if wizard validation fails during context-stocker plugin generation?

If wizard validation fails, the generator stops the template rendering process and prompts you to correct the invalid inputs against the wizard rules before proceeding to packaging.