skill-budget-eigenleistung-el

Plan and analyze employee-level Eigenleistung allocations using local BPLUS-NG data.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tobiascm/vobes-agent-vscode --skill skill-budget-eigenleistung-el
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-budget-eigenleistung-el
Source: https://github.com/tobiascm/vobes-agent-vscode/tree/main/.agents/skills/skill-budget-eigenleistung-el
Command: npx skills add https://github.com/tobiascm/vobes-agent-vscode --skill skill-budget-eigenleistung-el

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

EL planning and analysis for the BPLUS-NG integration is complex: it requires consolidating local EL data, validating month-level totals, and safely applying changes to allocations per EA while respecting booking restrictions. This Skill automates data retrieval from the local EL planning store, supports planning and adjustments (including zeroing months or rebalancing), and provides structured reports to guide decisions.

Core Features & Use Cases

  • Employee-level EL planning: fetch, analyze, and report EL allocations per EA for individuals.
  • Month-level edits with safety: enforce 100% monthly totals, honor booking locks, and provide dry-run vs. apply modes.
  • End-to-end EL workflows: generate detailed change reports via el_change.py and view consolidated insights via report_el.py.

Quick Start

Run a dry-run EL planning update for an employee and EA via the el_change.py tool.

Frequently Asked Questions about skill-budget-eigenleistung-el

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

FAQPage Schema
How do I plan and adjust Eigenleistung allocations for employees in BPLUS-NG?

To plan Eigenleistung (EL) allocations, use the el_change.py tool to query the local BPLUS-NG data and apply month-level changes per EA. The workflow supports dry-run modes and ensures 100% monthly total validation.

Can I compare Eigenleistung against Fremdleistung data for budget analysis?

Yes, you can compare Eigenleistung versus Fremdleistung data by running the report_el.py script. It retrieves consolidated insights from your local budget SQLite DB to guide allocation decisions.

What is the best way to safely apply month-level changes to EL planning without breaking totals?

The safest way to apply EL planning changes is using the dry-run mode in el_change.py. This enforces strict monthly total validation and honors booking locks before committing any adjustments to the staging workflow.

Do I need a local SQLite database to run EL planning and reporting workflows?

Yes, a local budget SQLite DB is required to run EL planning and reporting workflows. The report_el.py and el_change.py scripts depend on this local data store to query and validate employee-level allocations.

Why does my Eigenleistung planning update fail when booking locks are active?

Eigenleistung planning updates fail when booking locks are active because the system enforces strict monthly total validation. You must ensure lock checks are respected and use the staging workflow to safely apply changes.

Can I zero out specific months or rebalance EL allocations per EA?

Yes, you can zero out specific months or rebalance EL allocations per EA using the el_change.py tool. It allows month-level edits while enforcing 100% monthly totals and honoring booking restrictions.