Find the perfect capability for your agent.
Handle module attribute mapping and mapping history management in Unopim. Use this skill when creating module attribute mapping UI, mapping controller, mapping history, or restricting fields to module structure. Only Attribute Mapping and History tabs are allowed. Covers DB_PREFIX (auto-added by Laravel), Migration/ singular folder, HistoryTrait on models, flat ACL, cURL HTTP client, and JsonResponse controller pattern.
Fix common issues in geographic data contributions to the CSC database. Use this skill whenever you need to fix, correct, repair, patch, or resolve issues in a data contribution or PR. Trigger on: "@copilot fix this", "auto-fix" label on issues, "can you fix", "please correct", "help me fix", "what's wrong with my PR", removing auto-managed fields, correcting country codes, fixing mismatched foreign keys, or formatting JSON. Also use when a PR has validation errors and you need to commit fixes directly. Read common-fixes.md in this directory for fix patterns and examples.
Triage and classify new issues for the CSC database repository. Use this skill whenever an issue is opened, assigned to you, or needs classification. Trigger on: new issue triage, "classify this issue", "what type of issue is this", labelling requests, issue assignment, data correction reports, data addition requests, bug reports, feature requests, or any time you need to categorise, label, prioritise, or respond to a GitHub issue. Also use when deciding whether an issue can be auto-fixed or needs human intervention.
Validate geographic data contributions against the CSC database schema. Use this skill whenever you encounter a PR that adds, modifies, or deletes data in the contributions/ directory. Trigger on: validate, check, review, verify, audit, inspect, or assess any data contribution, PR review requests, schema compliance checks, field validation, or when someone says "is this correct", "check my data", "validate this", or "review my PR". Also use when asked about required fields, allowed values, or data format rules. Read schema-rules.md in this directory for the complete field specification.
Perform an intelligent review of geographic data PRs beyond schema validation. Use this skill whenever reviewing a data PR, performing code review on contributions, checking if data makes geographical sense, or assessing data quality. Trigger on: PR review requests for data changes, "review this PR", "does this look right", "is this data correct", quality assessment requests, geographic plausibility checks, suspicious pattern detection, or any pull request touching files in the contributions/ directory. This goes beyond schema validation to check real-world geographic accuracy.
Explains the project structure of the agent-framework .NET solution
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.
How to use the verify-samples tool to run, verify, and manage sample definitions in the Agent Framework repository. Use this when adding, updating, or running sample verification.
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
Guidelines for creating and modifying sample code in the Agent Framework Python codebase. Use this when writing new samples or updating existing ones.
Manage GitHub issues, labels, and project boards for the Arize-ai/phoenix repository. Use when filing roadmap issues, triaging bugs, applying labels, managing the Phoenix roadmap project board, or querying issue/project state via the GitHub CLI.
Screenshot a running Phoenix feature and attach images to a GitHub PR. Builds the frontend, starts Phoenix with env vars, uses agent-browser to capture screenshots, uploads to GCS, and updates the PR body.
Create Phoenix release documentation grounded in actual code changes. Use this skill whenever the user asks to write release notes, document a release, update release documentation, or mentions undocumented releases. Also trigger when the user wants to update GitHub release descriptions, add entries to the release notes page, or asks what changed in a recent Phoenix version.
End-to-end bug fix workflow for the Exposed project. Accepts a GitHub issue (#NUMBER), YouTrack issue (EXPOSED-NUMBER), or YouTrack URL (https://youtrack.jetbrains.com/issue/EXPOSED-NUMBER). Fetches the issue, creates a failing reproducer test, commits on a new branch, implements the fix, validates, and opens a PR. Use this skill whenever the user wants to fix a bug from an issue tracker, mentions a EXPOSED issue number, or references a GitHub issue to fix.
Fix a GitHub issue on OpenPipe/ART and open a PR. Use when the user asks to fix, solve, or work on an ART issue, or references a GitHub issue URL containing "OpenPipe/ART". Triggers: "fix ART issue", "solve this issue" with an OpenPipe/ART URL, "work on ART #N".
Triage and fix failing Buildkite CI checks for RisingWave pull requests by extracting concrete failing tests, diffs, and error messages from Buildkite build/job logs and artifacts, then applying focused code or test fixes. Use when users ask to diagnose red Buildkite checks, investigate flaky/failing CI jobs, understand why a Buildkite build failed, or provide Buildkite/GitHub check URLs and want a concrete fix.
