Adding a Ticker

Automate microservice ticker creation and modification in service.yaml with Go.

172|5|Updated Sep 9, 2022
One-click install
npx skills add https://github.com/microbus-io/fabric --skill adding-a-ticker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Adding a Ticker
Source: https://github.com/microbus-io/fabric/tree/main/.claude/skills/microbus/add-ticker
Command: npx skills add https://github.com/microbus-io/fabric --skill adding-a-ticker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to create or modify recurring operations (tickers) for microservices, reducing manual toil and ensuring consistent scheduling.

Core Features & Use Cases

  • Define tickers in service.yaml to schedule periodic work.
  • Generate boilerplate and scaffold code for new tickers.
  • Implement and test ticker logic, then document and version the microservice.

Quick Start

Define a new ticker in the microservice's service.yaml, run go generate to scaffold code, implement the business logic in service.go, and run the integration tests.

Frequently Asked Questions about Adding a Ticker

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

FAQPage Schema
How do I schedule recurring tasks in a microservice?

You schedule recurring microservice tasks by defining tickers in your service.yaml file, which specifies the tick interval and description to automate periodic work and reduce manual toil.

What is the best way to generate boilerplate code for a microservice ticker?

The best way to generate boilerplate for a microservice ticker is to define it in service.yaml and run go generate to scaffold the code. This enforces structured Go function signatures and ensures reliable ticker behavior.

Can I use service.yaml to configure tick intervals for periodic microservice work?

Yes, service.yaml is used to configure tick intervals for periodic microservice work. Defining the ticker in this file provides clear descriptions and enforces a structured workflow for reliable and repeatable scheduling.

How do I implement and test ticker logic after scaffolding the boilerplate?

You implement and test ticker logic by adding your business logic to the generated service.go file and then running integration tests. This validates the ticker behavior and ensures the recurring microservice tasks function correctly before deployment.

Does adding a ticker require an existing microservice workflow?

Adding a ticker requires an existing microservice workflow that uses service.yaml for configuration and supports go generate for code scaffolding. The Skill targets Go function signatures and structured workflows to ensure reliable ticker behavior.