Results for “protocol-submission”

Provides a structured protocol for receiving and evaluating code review feedback, emphasizing technical verification over performative agreement.

Follow a project's contribution guidelines when creating issues, branches, commits, and pull requests.

Generate standardized commit messages following the Conventional Commits specification using a structured XML format.

Provides a canonical facilitation protocol for interactive skills: one step at a time with progress tracking, adaptive recommendations, and interruption handling.

Apply Optionals, Protocols, Extensions, and Type Safety patterns in Swift. Use when working with Swift Optionals, Protocols, Extensions, or type-safe APIs.

Implements and manages Wave Terminal's WPS publish-subscribe event system, covering event type definition, publishing, subscribing, and TypeScript type generation.

Submits or updates a Wall of Apps entry in the App-Store-Connect-CLI repository using the `asc apps wall submit` command, with dry-run preview and confirmation.

Applies the same change across multiple repositories in parallel using git worktrees, tests, and pull requests.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Implements real-time pub/sub messaging with Ably's edge infrastructure, covering presence, message history, and token authentication.

Create a delivery plan with goals, capacity, scope, risks, and commitments.

Load this skill when the user says "update coding standards", "update-coding-standards", or "/update-coding-standards". Analyzes the diff of a merged PR and appends any valuable new patterns to the relevant coding standards doc — but only if something genuinely warrants documenting.

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

Write construction bid proposals with scope and pricing. TRIGGERS - Use when user needs help with bid-proposal related tasks.

Create informed consent forms for procedures. TRIGGERS - Use when user needs help with consent-form related tasks.

Write business proposals, RFP responses, statements of work, grant applications, and project pitches. Use when creating persuasive documents that secure funding, contracts, or approval. Also trigger for 'business proposal', 'RFP response', 'statement of work', 'SOW', 'grant proposal', 'project pitch', 'bid document', or 'proposal template'.

Imported skill protocol from langchain

Create informed consent forms for procedures. TRIGGERS - Use when user needs help with consent-form related tasks.

Reporting Templates

RSS Submission

Use when serving as a peer reviewer and deciding whether and how AI may assist, when a manuscript under review must never be pasted into an external tool, or when a confidentiality-preserving review and disclosure are needed.

Creates a complete change proposal with design, specs, and tasks in one step, ready for implementation.

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.