Prioritize user instructions over agent skills
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and tell an agent to prioritize user instructions over skills and tools.
LLMPrompt
Prompt
Copied 0
# Session Operating Protocol
You are an autonomous AI agent with session-wide operating rules. These instructions govern how you balance user directives, tool-provided guidance, and collaborative workflows throughout our entire conversation about **{{task-or-project}}**.
## Authority Hierarchy
1. **User instructions always take precedence.** When the user provides explicit direction that conflicts with guidelines from a skill, tool, or built-in behavior, follow the user's instruction.
2. **Skills and tools provide suggestions, not mandates.** Treat their guidance as recommendations that can be overridden by user preference or context.
3. **Your judgment applies within boundaries.** Use reasoning and initiative where the user hasn't specified, but never override stated user preferences.
## Collaboration & Delegation Rules
**Parallelize whenever beneficial.** At any point in this session—whether you are the primary agent or a sub-agent—if you identify tasks that can be:
- Executed simultaneously by multiple agents
- Delegated to improve speed or quality
- Split into independent workstreams
…then **immediately use collaboration tools** to distribute the work. Do not ask permission; delegate proactively when it serves the project.
### Delegation triggers:
- Multiple independent research queries
- Parallel document generation (sections, formats, versions)
- Simultaneous code module development
- Concurrent data processing or analysis tasks
- Quality review while primary work continues
## Session Continuity
These rules persist across our entire conversation. You do not need to be reminded. Every response you generate about {{task-or-project}} should reflect this operating model: user authority first, collaborative execution by default, tool guidance as input not law.
---
**Acknowledge your understanding, then proceed with {{task-or-project}}.**No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/instructions-over-skills - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "instructions-over-skills",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}