ibank-worklog-generator

Generate version-tagged iBank tb_worklog seed SQL from markdown and persona files.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-worklog-generator-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ibank-worklog-generator
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/ibank-worklog-generator
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill ibank-worklog-generator-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating and versioning iBank tb_worklog seed SQL is time-consuming and error-prone, especially when updating narrative wording, adding dependency links, or refreshing AI summaries across multiple worklog versions.

Core Features & Use Cases

  • Versioned Seed SQL Generation: Creates version-tagged tb_worklog seed SQL from team markdown files and persona configurations, supporting custom version tags like v3, v4, or v7.
  • Automated Dependency Linking: Generates matching predecessor dependency SQL for the same worklog version to maintain relational data integrity.
  • AI Summary Refresh: Updates tb_worklog.ai_summary fields without altering existing worklog row data such as request content, work content, status, or IDs. Use Case: If your team needs to release a new v7 batch of iBank worklog entries with updated wording to reduce repetition and linked predecessor records, this skill automates the entire SQL generation and validation workflow.

Quick Start

Ask the AI to generate a new v7 version of iBank worklog seed SQL with updated wording and matching dependency links from your existing team markdown and persona files.

Frequently Asked Questions about ibank-worklog-generator

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

FAQPage Schema
How do I generate versioned iBank worklog seed SQL for database seeding?

To generate versioned iBank worklog seed SQL, this skill automates creating version-tagged tb_worklog seed SQL files from team markdown and persona configurations, eliminating manual effort for database seeding workflows.

Can I update the AI summary fields on existing worklog records without losing row data?

Yes, you can refresh tb_worklog.ai_summary fields without altering existing row data such as request content, work content, status, or IDs, ensuring data integrity while updating AI summary update scripts.

What is the best way to add predecessor dependency links to iBank worklog SQL?

The best way to add predecessor dependency links is by generating matching dependency SQL automatically alongside the same worklog version, maintaining relational data integrity without manual SQL writing.

Do I need team markdown files to create a new batch of iBank worklog entries?

Yes, you need existing team markdown files and persona configurations as input sources to produce version-tagged seed SQL and associated dependency SQL for new worklog entry batches.

How do I reduce narrative repetition across multiple worklog versions?

To reduce narrative repetition, this skill supports generating updated narrative wording within new version-tagged tb_worklog seed SQL batches while preserving existing worklog row data integrity.