UPLB Tools
Official@uplbtools · Philippines
Open source tools for UPLB!
Agent Skills by UPLB Tools
Showing 10 vetted skills indexed across 1 GitHub repositories.
uplbtoolsdiscord-notifications
Diagnose and fix Discord notification delivery issues from Room TBA.
uplbtoolsrepo-baseline
Standardize repository workflows with minimal diffs and no secrets in commits.
uplbtoolsamis-term-import
Import AMIS class schedules into Room TBA by term_id.
uplbtoolsno-ai-slop
Apply Louis Rossmann's anti-AI-slop writing rules to prose.
uplbtoolsplaywright-e2e-ci
Automate Playwright end-to-end tests in GitHub Actions CI pipelines.
uplbtoolscontributor-proposals
Manage contributor edit proposals for a campus map application.
uplbtoolsponytail-review
Review code diffs for over-engineering patterns like YAGNI and unnecessary deletions.
uplbtoolsroom-tba-agent-workflow
Guide coding workflow for the Room TBA project with scoped edits and verification.
uplbtoolsagent-handoff
Generate structured handoff prompts for multi-agent workflows.
uplbtoolsvercel-supabase-ops
Manage Vercel deployments and Supabase database migrations for the Room TBA project.
Frequently Asked Questions About UPLB Tools
FAQPage SchemaWhat specific tasks are enabled by these repository standards?▼
These standards enable consistent repository hygiene by enforcing secret-free commits and minimizing diff noise. They facilitate structured code reviews focused on YAGNI principles, ensuring that campus-based projects remain maintainable and free from over-engineering patterns during the development lifecycle.
Which personas benefit from these campus-specific development utilities?▼
Campus software developers, student contributors, and project maintainers managing the Room TBA ecosystem benefit most. These utilities are designed for engineers requiring standardized deployment paths for Vercel and Supabase, alongside those managing academic data imports from AMIS systems.
What are the prerequisites for implementing these repository configurations?▼
Implementation requires an existing GitHub environment and familiarity with Playwright for end-to-end testing. Users must have administrative access to Vercel and Supabase instances to execute database migrations and deployment operations as defined in the project baseline.