writing-documentation
Use when writing or updating any documentation - README, website docs, or skills. Covers quality standards, example validation, and DRY patterns.
Découvrez les skills DevOps, comparez leurs dépôts et consultez leurs instructions.
Use when writing or updating any documentation - README, website docs, or skills. Covers quality standards, example validation, and DRY patterns.
Use when creating a new walkerOS source. Example-driven workflow starting with research and input examples before implementation.
Use when working with transformers, understanding event validation/enrichment/redaction, or learning about transformer chaining. Covers interface, return values, and pipeline integration.
Use when events aren't reaching destinations, debugging event flow, or troubleshooting mapping issues. Covers common problems and debugging strategies.
Use when working with sources, understanding event capture, or learning about the push interface. Covers browser, dataLayer, and server source patterns.
Use when creating a new walkerOS transformer. Example-driven workflow for validation, enrichment, or redaction transformers.
Use when creating a new walkerOS destination. Example-driven workflow starting with research and examples before implementation.
Use when configuring event mappings for specific use cases. Provides recipes for GA4, Meta, custom APIs, and common transformation patterns.
Use when contributing to walkerOS, before writing code, or when unsure about project conventions. Covers build/test/lint workflow, XP principles, folder structure, and package usage.
Use when working with sources/destinations to understand standard logging patterns, replace console.log, or add logging to external API calls. Covers DRY principles, when to log, and migration patterns.
Use when learning walkerOS architecture, understanding data flow, or designing composable event pipelines. Covers Source→Collector→Destination pattern and separation of concerns.
Use when creating events, understanding event structure, or working with event properties. Covers entity-action naming, event properties, statelessness, and vendor-agnostic design.
Use when transforming events at any point in the flow (source→collector or collector→destination), configuring data/map/loop/condition, or understanding value extraction. Covers all mapping strategies.
Use when writing tests, reviewing test code, or discussing testing approach for walkerOS packages. Covers env pattern, dev examples, and package-specific strategies.
Use mcpc CLI to interact with MCP servers - call tools, read resources, get prompts. Use this when working with Model Context Protocol servers, calling MCP tools, or accessing MCP resources programmatically.
Skill for designing and implementing backend APIs. Includes Zero Script QA methodology for validating APIs without test scripts. Use proactively when user needs to design or implement backend APIs. Triggers:...
9-phase Development Pipeline complete knowledge. Use when user doesn't know development order or starts a new project from scratch. Use proactively when user asks about development order, phases, what to do fi...
Analyzes existing codebases to understand structure, patterns, and technical debt
Validates plans before execution to catch issues early
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification
Requires proof before marking work complete — no "trust me, it works"
Monitors context complexity and triggers state dumps before quality degrades
Validates implemented work against spec requirements with empirical evidence
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.