Skip to content
Agentmart
Submit a tool

orchestration

Skill by prathamchopra001

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/prathamchopra001-orchestration

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

The publisher has not written a description yet.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
orchestration
Description
None
License
MIT
Instructions
67 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • missing YAML frontmatter
  • name: missing
  • description: missing

Files (2)

  • SKILL.md
  • skill_meta.json

SKILL.md (first lines)

# SKILL.md: Orchestration

## Task Description  
Decompose complex objectives into specific, answerable questions that align with the research domain and methodology. Ensure questions are actionable, focused, and directly address the core objective.

## Output Format  
```json
{
  "questions": ["Specific question 1", "Specific question 2", ...],
  "rationale": "Explanation of how the questions address the objective"
}
```  
- **questions**: Array of 5-10 answerable questions starting with "What", "How", "Why", "Which", or "To what extent".  
- **rationale**: 1-2 sentences explaining the decomposition logic and alignment with the objective.

## Decision Framework  
1. **Identify Core Objective**: Extract the main goal from the input.  
2. **Break into Sub-Questions**: Use "What", "How", "Why" to split the objective into smaller parts.  
3. **Ensure Specificity**: Avoid vague terms; specify variables, methods, or contexts.  
4. **Confidence Scoring**:  
   - Score 1-5: 5 = precise and answerable, 1 = too broad or unclear.  
   - Prioritize questions with higher scores.  
5. **Edge Cases**:  
   - If the objective is ambiguous, ask for clarification.  
   - For domain-specific terms, define them in the rationale.  

## Common Patterns  
**Example 1**  
Input: *"What are the key factors affecting Q-learning convergence?"*  
Output:  
```json
{
  "questions": [
    "How do hyperparameters influence Q-learning convergence rates?",
    "What role does reward function design play in Q-learning stability?",
    "Which environments exhibit the fastest Q-learning convergence?"
  ],
  "rationale": "These questions focus on hyperparameters, reward functions, and environment-specific factors, which are actionable and directly tied to the objective."
}
```  

**Example 2**  
Input: *"How can we improve patient adherence to treatment plans?"*  
Output:  
```json
{
  "questions": [
    "What barriers do patients face when adhering to treatment plans?",
    "How does telehealth impact medication adherence in chronic disease management?",
    "Which interventions show the highest adherence rates in clinical trials?"
  ],
  "rationale": "The questions address barriers, telehealth impact, and effective interventions, providing a structured approach to improving adherence."
}
```  

## Anti-Patterns  
- **Too Broad**: *"What is Q-learning?"* (Not answerable via data analysis).  
- **Unfocused**: *"How can we improve everything?"* (Lacks specificity).  
- **Irrelevant Questions**: *"What is the meaning of life?"* (Off-topic).  
- **Missing Rationale**: Omitting the explanation for decomposition logic.  

## Quality Checklist  
1. Validate JSON structure matches the schema.  
2. Ensure all questions are answerable via literature or data.  
3. Confirm questions are specific, not vague or overly broad.  
4. Verify the rationale explains how the questions align with the objective.  
5. Check for domain-specific terminology and ensure it’s clearly addressed.

From prathamchopra001/INQUIRO, MIT.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Mar 11, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

orchestration skill. Agent Mart. https://agentmart.dev/skills/prathamchopra001-orchestration (last updated 2026-10-24)