skills.rest
fieldsphere
fieldsphereOFFICIAL
Explore all skills by this author →
GitHub

agent-naming

Automate Cursor agent naming with ticket-backed and four-word Title Case patterns.

37|20|Updated Mar 2, 2026
Search Tags:#productivity#naming-conventions#cursor#agent-naming#ticket-backed#title-case
One-click install
npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill agent-naming
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-naming
Source: https://github.com/fieldsphere/cursor-team-marketplace-template/tree/main/plugins/cursor-starter-pack/skills/agent-naming
Command: npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill agent-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent agent naming makes it harder to quickly identify active agents across the Cursor workspace. This skill standardizes how names are formed so teams can scan and manage sessions faster.

Core Features & Use Cases

  • Ticket-backed naming: When a work item exists, uses {TICKET-ID}: {Description} to tie agents to the task.
  • Non-ticket naming: When there is no ticket, uses Title Case with at most four words for clarity.
  • Lifecycle consistency: Enforces consistent renaming when tickets are created or closed to preserve history.

Quick Start

Start naming a new agent using the ticket-backed pattern when a ticket exists, otherwise use the four-word Title Case pattern.

Frequently Asked Questions about agent-naming

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

FAQPage Schema
How do I keep Cursor agent names consistent across different sessions?▼

Cursor agent naming standardizes identification by enforcing the ticket-backed pattern {TICKET-ID}: {Description} or the non-ticket pattern using Title Case with a maximum of four words, ensuring agents remain traceable across cloud, local, and background environments.

What is the best way to name a Cursor agent linked to a Jira or support ticket?▼

Ticket-backed Cursor agent naming uses the pattern {TICKET-ID}: {Description} to tie agents to specific work items. This ensures active agents are easily identified and their history is preserved during lifecycle changes across the workspace.

Can I use Title Case naming for Cursor agents when there is no ticket?▼

Title Case formatting is required for non-ticket Cursor agent naming. The pattern enforces a maximum of four words formatted in Title Case, ensuring agent names remain clear and scannable without an associated ticket ID.

Does consistent agent naming work for local and background Cursor sessions?▼

Consistent agent naming applies to cloud, local, and background Cursor agents. The standardization process works across all environments during agent creation or renaming, ensuring teams can quickly identify and manage active sessions workspace-wide.

Why does my Cursor agent history become hard to trace after renaming?▼

Agent history becomes hard to trace without lifecycle consistency in naming. Enforcing standardized patterns during ticket creation or closure preserves history and ensures agents remain identifiable across the Cursor workspace.

Related Skills

Explore More Product & Management Skills→
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
hendrax5hendrax5

audit

Returned successfully.

Community
Intermediate
automatedigitalautomatedigital
1

tasker

Automate ticket lifecycle from ideation to merged pull request across ticket trackers and GitHub.

Official
Advanced
portermetricsampleportermetricsample
17

meta-ads-naming-conventions

Generate Meta Ads naming specs and UTM templates from SUMAS levers.

Community
Intermediate