Audits an existing repository against BazelStarterTemplate and brings it in line, one concern at a time - hermetic Bazel build, devenv and git hooks, format/lint tests, unit tests and coverage, conventional commits and release-please, CI, OCI image, documentation, CLAUDE.md - or upgrades a project created from the template to a newer template release. Use when the user asks to review, audit, standardize, clean up, modernize or "make consistent" a repository's infrastructure, to add CI, linting, formatting, releases, Docker/OCI images or docs to an existing project, to migrate a project to Bazel, or to update a project to the latest template.
calmette54/BazelStarterTemplate
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments. Ready means the code works and achieves a stated goal, verified by your own tests and/or, if you deem it necessary, human testing.
AI-powered visual testing and accessibility setup for iOS/SwiftUI apps. Build, launch in Simulator, test with computer use, detect crashes, analyze memory leaks, and add accessibility identifiers — all from the terminal.
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by verifying work is complete (tests, requirements, code review, TDD compliance) and presenting structured options for merge, PR, or cleanup
Connect an arbitrary REST API to the PostHog data warehouse as a Custom source by authoring a JSON manifest, with no per-source code. Use when the user points at an API that has no built-in PostHog connector — "import data from this REST API", "sync my internal API", "connect this API from its docs", "build a custom data warehouse source" — and gives a docs URL or a natural-language description of the endpoints. Walks through drafting the RESTAPIConfig manifest (auth — bearer, API key, HTTP basic, or OAuth2 client credentials / refresh token — pagination, record path, incremental cursor, parent/child fan-out), validating it, test-reading live rows to verify the field mappings, and creating the source. If the API already has a native PostHog connector, use setting-up-a-data-warehouse-source instead — this skill checks the connector registry first and only handles APIs with no native connector.
Use when a solution needs a coherent structure before implementation or production for Software implementation and code architecture: Swift and iOS apps for API evolution. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Test migration from supported old and new versions with a disposable dataset and a documented recovery path. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Run the every-10-pushes quality checkpoint — a scoped code review of everything since the last checkpoint, plus a test-and-lint debug pass. Use this skill whenever a hook reports that a push count hit a multiple of 10, whenever the user types /push-checkpoint, and whenever the user asks for a checkpoint, a periodic review, a "review the last batch of work" pass, or asks what has accumulated since the last review. Prefer this over an ad-hoc review whenever the request is about reviewing recent pushes as a batch.
Diseña y optimiza pipelines de CI/CD — GitHub Actions, GitLab CI, automatización de tests, linting, builds y deploys. Trigger: Cuando hay que automatizar tests, linting, builds o deploys, o configurar un pipeline de CI/CD.
Angular frontend conventions, patterns, and test infrastructure. Use when working with Angular components, services, modules, RxJS, Angular CLI, ng commands, Jasmine tests, Component Harnesses, HttpTestingController, Angular routing, Angular forms, Angular pipes, or Angular dependency injection.
Add a reference-image test to Lodestone, or deliberately update reference images after an intended rendering change. Use when a rendering feature needs image coverage, or a reference-image test fails because rendering was meant to change.
This skill should be used when the user asks about "test doubles", "mocking", "stubbing", "spies", "verifying doubles", "partial doubles", "allow", "receive", "have_received", or needs guidance on isolating tests and mocking dependencies in RSpec.
End-to-end procedure for porting any Flutter/Dart file from the poc_vedaxl app into this React Native monorepo (models, repositories, services, state, widgets, screens, navigation, l10n). Use it whenever you start, continue or review the port of a `lib/**/*.dart` file, when you're asked "port X", "convert this Dart file", "where does <dart file> go", or when you need the Flutter→RN concept mapping (widgets, ChangeNotifier, FutureBuilder, Navigator, ThemeData, sheets, animations, CustomPainter, ARB). For a single screen use flutter-screen-to-rn; for models/repositories use dart-model-to-ts; for tests use flutter-test-to-jest.
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.
Use when a task is well-defined, has an automatic way to verify success (tests, linter, build), and is tedious or large enough to benefit from unattended iteration - e.g. "get all tests passing", "implement this spec end to end", "fix every lint error". Not for one-shot changes or work that needs human judgment mid-stream.
Expert VBA code reviewer for Excel/Word/Outlook/PowerPoint macros and add-ins. Use this skill whenever the user pastes VBA and asks for a review, audit, feedback, or help improving it. Also trigger when the user reports a bug, a slow macro, a wrong UDF result, a workbook that won't close, or unexpected Office behavior and shares VBA as context — even without the word "review". Trigger on phrases like "what's wrong with this macro", "can you check this VBA", "is this correct", "why is this slow", "review my macro", or any paste of VBA followed by a question. Prioritize correctness over style: check Option Explicit, declaration bugs, error handling, range/array performance, and application-state hygiene before anything cosmetic. Because VBA has no external CI, a review must also say how to *verify* a fix inside the host Office app. For C#/VB.NET Office add-ins use VSTO-review instead; to author the tests a review asks for, use vba-code-test-writing.
Use when working in the Vivreal Portal (Vivreal_Portal_Mobile), a Next.js 16 App Router web app despite the "Mobile" name. Covers the proxy-route layer (createProxyHandler factory vs hand-written), the three-tier API client rule (createAuthAxios / publicAxios / fetch), the four backend upstreams, auth cookies (token + active_ctx), the retired in-app agent (AI is MCP only), feature flags, PWA shell traps, offline honesty, the Socials and Channels screens, SSR-safe patterns, and e2e/unit test gates. Triggers on: portal, Vivreal_Portal_Mobile, proxy route, createAuthAxios, createProxyHandler, active_ctx, AuthContext, edge runtime, basePath /app, site analytics dashboard, social hub, AI FAB, agent drawer, EditPlan, feature flags, Instagram inbox, reach-out console (formerly cold-call), demo-account claim flow, site template picker, Studio editor, dashboard insights, account deletion, e2e testing, coverage map. Source of truth: Vivreal_Portal_Mobile CLAUDE.md at origin/stable (recount src/app/api/proxy/).
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.