a-plus-onboard-correction

Generate Ruby scripts to correct Attendance Plus entity configurations for a district.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/dailydm/skills --skill a-plus-onboard-correction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a-plus-onboard-correction
Source: https://github.com/dailydm/skills/tree/main/a-plus-onboard-correction
Command: npx skills add https://github.com/dailydm/skills --skill a-plus-onboard-correction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Generate throwaway Ruby scripts to correct Attendance Plus entity configurations for a district after onboarding, reducing manual post-go-live fixes.

Core Features & Use Cases

  • Creates, updates, and discards absence codes and calendar adjustments via well-structured scripts.
  • Supports dry-run validation and per-district execution to minimize risk before applying changes.
  • Uses templates and references in assets/references to guide script generation and execution.

Quick Start

Run the generator with the district_id and desired changes, then review the dry-run output before applying.

Frequently Asked Questions about a-plus-onboard-correction

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

FAQPage Schema
How do I generate Ruby scripts to correct Attendance Plus absence codes after district onboarding?

Generate one-off Ruby scripts to correct Attendance Plus absence codes by providing a district_id and per-change mappings. The Skill uses asset templates to structure the script and applies updates specifically for the target district's onboarding corrections.

How does the dry-run workflow validate Attendance Plus configuration changes before applying them?

The dry-run workflow validates Attendance Plus configuration changes by generating a Ruby script that tests per-district updates, such as school-year dates and tier thresholds, allowing you to review the output before committing changes to the live district environment.

Can I update school-year dates and non-instructional days for a specific district using Ruby automation?

Yes, you can update school-year dates and add non-instructional days by running the generated Ruby scripts with the district_id. The automation applies these calendar adjustments across the specified district using structured templates.

What prerequisite inputs do I need to adjust Attendance Plus tier thresholds across multiple districts?

Adjusting Attendance Plus tier thresholds requires a district_id and specific per-change mappings. These inputs drive the Ruby script generation, ensuring the configuration updates target the correct district entities.

Are there limitations when using district scripts to fix Attendance Plus entity configurations post-go-live?

The generated district scripts are designed as throwaway Ruby scripts for post-onboarding corrections rather than permanent integrations. They target specific entity configurations like absence codes and calendar adjustments, requiring dry-run validation before applying changes.