push

Create external backend tickets from wiki task pages with cross-references.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --skill push-brandtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: push
Source: https://github.com/brandtam/rubber-ducky/tree/main/src/skills/push
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill push-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams move work tracked in a wiki into external ticketing backends (GitHub, Jira, Asana, etc.) by drafting and creating tickets from wiki pages, ensuring traceability and cross-referencing.

Core Features & Use Cases

  • Reads a wiki task's frontmatter and body to draft a backend ticket.
  • Detects configured backends in the workspace and attaches the appropriate references and labels.
  • Uses the ticket-writer agent and a confirm-token gate to safely create tickets and update wiki frontmatter with references.

Quick Start

Describe a wiki task and tell it to push to the configured backend as a new ticket.

Frequently Asked Questions about push

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

FAQPage Schema
How do I push wiki tasks to an external ticketing backend as tickets?

To push wiki tasks to an external ticketing backend, this skill reads task frontmatter, drafts a ticket, and creates cross-references across systems using a configured backend and the ticket-writer agent.

What backends can I use to create tickets from wiki frontmatter?

You can create tickets from wiki frontmatter using configured external backends like GitHub, Jira, or Asana, provided the workspace defines the backend and grants access to the ticket-writer agent.

How does cross-linking work between wiki pages and external ticketing systems?

Cross-linking between wiki pages and external ticketing systems works by drafting a ticket from the wiki body and safely updating wiki frontmatter with backend references to ensure traceability.

Do I need a confirm-token flow to automate creating tickets from wiki pages?

Yes, automating ticket creation from wiki pages requires a confirm-token flow via the rubber-ducky CLI to safely perform the create operation and update task frontmatter with references.

What is the best way to move work tracked in a wiki into external backends?

The best way to move work tracked in a wiki into external backends is using a skill that detects configured backends, drafts tickets from task pages, and attaches appropriate labels and cross-references.

Why does pushing a wiki task to a backend require a ticket-writer agent?

Pushing a wiki task to a backend requires a ticket-writer agent to safely draft the ticket content and execute the create operation through a gated confirm-token flow via the rubber-ducky CLI.