lark-backlog-sync

Upload epics and stories to Lark Base via the Avila Tools API.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill lark-backlog-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lark-backlog-sync
Source: https://github.com/Avila-Tek/avila-tek-skill-pack/tree/main/skills/planning-6-write-epics-and-hu-in-base
Command: npx skills add https://github.com/Avila-Tek/avila-tek-skill-pack --skill lark-backlog-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the synchronization of epics and user stories from a local repository to a Lark Base via the Avila Tools API. It also handles translation of content to Spanish and ensures records are upserted to the project management base. Trigger phrases include: "sync to Lark", "push epic to Lark", "load backlog to Lark Base", "carga la épica al Lark", "sincroniza el backlog", "push E-002 to Lark".

Core Features & Use Cases

  • Sync epics and stories from the local repo to Lark Base via the Avila Tools API, upserting records to keep the backlog consistent.
  • Translate all content fields to Spanish while preserving IDs, statuses, and structure.
  • Use cases include pushing new epics and stories, updating existing backlog items, and loading a project's backlog into Lark Base for visibility.

Quick Start

Provide the required inputs and run the skill in your project directory to sync backlog to Lark Base.

Frequently Asked Questions about lark-backlog-sync

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

FAQPage Schema
How do I sync epics and stories from a local repository to Lark Base?

This skill pushes backlog items to Lark Base by upserting records via the Avila Tools API. It translates content to Spanish while preserving IDs, statuses, and structure during the synchronization process.

Can I translate backlog content to Spanish when pushing to Lark Base?

Yes, when pushing backlog items to Lark Base, the skill translates all content fields to Spanish. It automatically handles the translation while preserving the original IDs, statuses, and structural formatting of the epics and stories.

What do I need to upload my project backlog to Lark Base?

To upload your project backlog to Lark Base, you need an Avila Tools API endpoint URL, a valid API key, and the specific backlog item IDs you want to sync. The skill runs in your local project directory to execute the push.

Does syncing backlog items to Lark Base update existing records or create new ones?

Syncing backlog items to Lark Base upserts records, meaning it updates existing epics and stories if they are already present, or creates new ones. This ensures your project management base remains consistent with your local repository.

How do I push a specific epic to Lark Base using an API?

You can push a specific epic to Lark Base by providing its specific backlog item ID to the skill. Using the Avila Tools API, the skill targets that individual epic or story and upserts it directly into the project management base.