analyze-request
Skill0 starsChanged 8 months agoMITView on GitHub
Understand user's analysis request through structured dialog, score complexity, and route to appropriate execution mode. Use when user wants to analyze data.
- Reads credentials
In this repositoryOne other file it gives its agents.
- execute-autoSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
If user provides forbidden path, respond: "Sorry, for security reasons, I can only access files within the current project directory."
- Distinctive: line 38
Ask questions ONE AT A TIME to clarify the request.
- Very specific: line 40
Use question templates from references/question-templates.md.
- Distinctive: line 120
If security validation fails → Explain why and ask for different path
- Distinctive: line 121
If complexity scoring fails → Fall back to rule-based scoring
- Distinctive: line 122
If user provides incomplete info → Ask follow-up questions
- Distinctive: line 123
If task is too vague → Help decompose into specific questions
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Analyze Request Skill
Request understanding and routing for DA-Agent
Purpose
Transform vague business requests into structured analysis tasks, score complexity, and route to the appropriate execution mode.
Security Constraints
CRITICAL: Before any file operation, validate paths:
from lib.security_wrapper import SecureFileAccess
security = SecureFileAccess(os.getcwd())
safe_path = security.validate_path(user_provided_path)Never access:
- Files outside current working directory
- .env files
- Credential files
- .ssh directories
If user provides forbidden path, respond: "Sorry, for security reasons, I can only access files within the current project directory."
Workflow
Phase 1: Structured Dialog
Ask questions ONE AT A TIME to clarify the request. Use multiple choice when possible.
Use question templates from references/question-templates.md.
Required information:
- Core question - What business question are we answering?
- Data sources - Which files? (validate with security wrapper)
- Time range - What period?
- Dimensions - How to slice the data?
- Analysis type - What kind of analysis?
Phase 2: Complexity Scoring
Once you have structured requirements, score complexity:
from lib.complexity_scorer import ComplexityScorer
scorer = ComplexityScorer()
result = scorer.score(structured_req)
print(f"Complexity Score: {result.score}/10")
print(f"Suggested Mode: {result.mode}")
print(f"Reasoning: {result.reasoning}")See references/complexity-scoring-rubric.md for scoring criteria.
Phase 3: User Confirmation
Present the scoring result and ask for confirmation:
Example:
Analysis Task Complexity
Score: 5/10 Suggested Mode: Collaborative Reasoning: Multi-file JOIN (2pts) + Funnel analysis (2pts) + Business rules (1pt)
In collaborative mode:
- I'll generate code drafts for your review
- You'll approve at key decision points
- We'll work together on the analysis
Proceed with this approach?
Phase 4: Route to Execution
Based on confirmed mode:
auto→ Load execute-auto skill and hand offcollab→ (Phase 2: Coming soon)assist→ (Phase 2: Coming soon)
For auto mode:
# Hand off to execute-auto skill
print("Routing to auto-execution mode...")
# The execute-auto skill will take over from hereThen follow the execute-auto skill workflow.
Phase 5: Knowledge Base Recording
Save the task to knowledge base:
from lib.knowledge_store import KnowledgeStore
import os
kb = KnowledgeStore(Path.home() / ".da-agent" / "knowledge")
task_id = kb.save_task(
description=original_request,
structured_req=structured_req,
complexity_score=result.score,
execution_mode=result.mode
)Error Handling
- If security validation fails → Explain why and ask for different path
- If complexity scoring fails → Fall back to rule-based scoring
- If user provides incomplete info → Ask follow-up questions
- If task is too vague → Help decompose into specific questions
Examples
See references/question-templates.md for conversation flow examples.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

