walkeros-create-source

Create walkerOS sources through a phased, example-driven workflow with templates and tests.

342|21|Updated Mar 14, 2022
One-click install
npx skills add https://github.com/elbwalker/walkerOS --skill walkeros-create-source
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: walkeros-create-source
Source: https://github.com/elbwalker/walkerOS/tree/main/skills/walkeros-create-source
Command: npx skills add https://github.com/elbwalker/walkerOS --skill walkeros-create-source

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to bootstrap a walkerOS source project from scratch, lacking a consistent, example-driven workflow. This skill provides a phased blueprint that starts with research, collects input examples, defines mappings, and then scaffolds code and tests. It ensures a repeatable, shareable approach to building new sources that align with walkerOS architecture.

Core Features & Use Cases

  • Phase-driven development: research, example creation, mapping, scaffolding, implementation, testing, and documentation.
  • Template-driven scaffolding: reuse standard source templates for web and server, with test and dev configurations.
  • Documentation-first workflow: generate ready-to-publish skill metadata and examples that drive validation.
  • Use Case: a team creates a new "data-source" to capture custom events and map them to walkerOS events with deterministic validation.

Quick Start

Begin by reviewing this Skill and following its seven phases to scaffold a new walkerOS source, including collecting inputs, defining mappings, implementing code, and validating with tests.

Frequently Asked Questions about walkeros-create-source

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

FAQPage Schema
How do I create a custom walkerOS source for capturing and mapping events?

You can build a walkerOS source by following a phased workflow: research, collect input examples, define mappings, scaffold code and tests, implement, and document. This ensures repeatable, shareable source creation aligned with walkerOS architecture.

What is the best way to structure a walkerOS source development workflow?

The best way to structure walkerOS source development is through a documentation-first, example-driven approach. Begin with research and input examples to define mappings before scaffolding code, ensuring deterministic validation and ready-to-publish metadata.

Can I use TypeScript to scaffold and test a new walkerOS source?

Yes, you can use TypeScript to scaffold and test a new walkerOS source. The workflow provides template-driven scaffolding with standard source templates for web and server, including test and development configurations.

Do I need a SKILL.md file to start building a walkerOS source?

Yes, you need a SKILL.md file with frontmatter containing a name and description to start building a walkerOS source. This metadata is required to output ready-to-publish skill metadata and drive the example-based validation.

Why does my walkerOS source implementation lack consistent event mapping?

Your walkerOS source implementation may lack consistent event mapping if you skip the research and example collection phases. Defining mappings from input examples before scaffolding ensures deterministic validation and architectural alignment.