--- name: base-v2 description: "LibreOffice Base workflow skill. Use this skill when the user needs Database management, forms, reports, and data operations with LibreOffice Base and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: backend tags: ["base-v2", "base", "database", "management", "forms", "reports", "and", "data"] complexity: intermediate risk: safe tools: ["codex-cli", "claude-code", "cursor", "gemini-cli", "opencode"] source: community author: "sickn33" date_added: "2026-04-17" date_updated: "2026-04-25" --- # LibreOffice Base ## Overview This public intake copy packages `plugins/antigravity-awesome-skills/skills/libreoffice/base` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. # LibreOffice Base Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Capabilities, Python Libraries, Limitations. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Creating new databases in ODB format - Connecting to external databases (MySQL, PostgreSQL, etc.) - Automating database operations and reports - Creating forms and reports - Building database applications - Use when the request clearly matches the imported source intent: Database management, forms, reports, and data operations with LibreOffice Base. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `SKILL.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `SKILL.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. ### Creating a New Database #### Method 1: Command-Line bash soffice --base #### Method 2: Python with UNO python import uno def createdatabase(): localctx = uno.getComponentContext() resolver = localctx.ServiceManager.createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", localctx ) ctx = resolver.resolve( "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext" ) smgr = ctx.ServiceManager doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx) doc.storeToURL("file:///path/to/database.odb", ()) doc.close(True) ### Connecting to External Database python import uno def connecttomysql(host, port, database, user, password): localctx = uno.getComponentContext() resolver = localctx.ServiceManager.createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", local_ctx ) ctx = resolver.resolve( "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext" ) smgr = ctx.ServiceManager doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx) datasource = doc.getDataSource() datasource.URL = f"sdbc:mysql:jdbc:mysql://{host}:{port}/{database}" datasource.Properties["UserName"] = user datasource.Properties["Password"] = password doc.storeToURL("file:///path/to/connected.odb", ()) return doc 2. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 3. Read the overview and provenance files before loading any copied upstream support files. 4. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. 5. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes. 6. Validate the result against the upstream expectations and the evidence you can point to in the copied files. 7. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity. ### Imported Workflow Notes #### Imported: Workflows ### Creating a New Database #### Method 1: Command-Line ```bash soffice --base ``` #### Method 2: Python with UNO ```python import uno def create_database(): local_ctx = uno.getComponentContext() resolver = local_ctx.ServiceManager.createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", local_ctx ) ctx = resolver.resolve( "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext" ) smgr = ctx.ServiceManager doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx) doc.storeToURL("file:///path/to/database.odb", ()) doc.close(True) ``` ### Connecting to External Database ```python import uno def connect_to_mysql(host, port, database, user, password): local_ctx = uno.getComponentContext() resolver = local_ctx.ServiceManager.createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", local_ctx ) ctx = resolver.resolve( "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext" ) smgr = ctx.ServiceManager doc = smgr.createInstanceWithContext("com.sun.star.sdb.DatabaseDocument", ctx) datasource = doc.getDataSource() datasource.URL = f"sdbc:mysql:jdbc:mysql://{host}:{port}/{database}" datasource.Properties["UserName"] = user datasource.Properties["Password"] = password doc.storeToURL("file:///path/to/connected.odb", ()) return doc ``` #### Imported: Overview LibreOffice Base skill for creating, managing, and automating database workflows using the native ODB (OpenDocument Database) format. #### Imported: Core Capabilities ### 1. Database Creation - Create new ODB databases from scratch - Design tables, views, and relationships - Create embedded HSQLDB/Firebird databases - Connect to external databases ### 2. Data Operations - Import data from CSV, spreadsheets - Export data to various formats - Query execution and management - Batch data processing ### 3. Form and Report Automation - Create data entry forms - Design custom reports - Automate report generation - Build form templates ### 4. Query and SQL - Visual query design - SQL query execution - Query optimization - Result set manipulation ### 5. Integration - Command-line automation - Python scripting with UNO - JDBC/ODBC connectivity ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @base-v2 to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @base-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @base-v2 for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @base-v2 using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ### Imported Usage Notes #### Imported: Command-Line Reference ```bash soffice --headless soffice --base # Base ``` ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - Use parameterized queries - Create indexes for performance - Backup databases regularly - Use transactions for data integrity - Store ODB source files in version control - Document database schema - Use appropriate data types ### Imported Operating Notes #### Imported: Best Practices 1. Use parameterized queries 2. Create indexes for performance 3. Backup databases regularly 4. Use transactions for data integrity 5. Store ODB source files in version control 6. Document database schema 7. Use appropriate data types 8. Handle connection errors gracefully ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills/skills/libreoffice/base`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ### Imported Troubleshooting Notes #### Imported: Troubleshooting ### Cannot open socket ```bash killall soffice.bin soffice --headless --accept="socket,host=localhost,port=8100;urp;" ``` ### Connection Issues - Verify database server is running - Check connection string format - Ensure JDBC/ODBC drivers are installed - Verify network connectivity ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/n/a` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | ### Imported Reference Notes #### Imported: Database Connection Reference ### Supported Database Types - HSQLDB (embedded) - Firebird (embedded) - MySQL/MariaDB - PostgreSQL - SQLite - ODBC data sources - JDBC data sources ### Connection Strings ``` # MySQL sdbc:mysql:jdbc:mysql://localhost:3306/database # PostgreSQL sdbc:postgresql://localhost:5432/database # SQLite sdbc:sqlite:file:///path/to/database.db # ODBC sdbc:odbc:DSN_NAME ``` #### Imported: Resources - [LibreOffice Base Guide](https://documentation.libreoffice.org/) - [UNO API Reference](https://api.libreoffice.org/) - [HSQLDB Documentation](http://hsqldb.org/) - [Firebird Documentation](https://firebirdsql.org/) #### Imported: Python Libraries ```bash pip install pyodbc # ODBC connectivity pip install sqlalchemy # SQL toolkit ``` #### Imported: Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. --- Source attribution: Munir Abbasi; Nikolas Hor Original project: https://github.com/sickn33/agentic-awesome-skills/blob/6dd1307be6462397eff16f34aeff282eac93cbc3/skills/libreoffice/base/SKILL.md License: MIT + CC-BY-4.0 License information: https://creativecommons.org/licenses/by/4.0/ Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2026 Omni Skills Team Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Creative Commons Attribution 4.0 International (CC BY 4.0) Original documentation and non-code content in this repository is licensed under CC BY 4.0, unless a more specific upstream license applies. You are free to: - Share — copy and redistribute the material in any medium or format - Adapt — remix, transform, and build upon the material for any purpose Under the following terms: - Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. Full license text: https://creativecommons.org/licenses/by/4.0/legalcode # Dave AI resource metadata Creator / publisher: Munir Abbasi; Nikolas Hor Original project: https://github.com/sickn33/agentic-awesome-skills/blob/6dd1307be6462397eff16f34aeff282eac93cbc3/skills/libreoffice/base/SKILL.md Attribution basis: Original workflow contribution and credited developers identified in Git history Fields of work: Data & Analytics, Development & Engineering Roles: Backend Developer, Data Analyst, Database Administrator Specialties: Database Tools: Libreoffice Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 07a82dca846f718bb62da4ce0fb3da8fbb823e9a02bc49f4bacf01ba4df34f9d Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.