sky-dev 0.1.6__tar.gz → 0.1.7__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {sky_dev-0.1.6 → sky_dev-0.1.7}/CHANGELOG.md +4 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/PKG-INFO +1 -1
- {sky_dev-0.1.6 → sky_dev-0.1.7}/pyproject.toml +1 -1
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/__init__.py +1 -1
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/mode_prompts.py +12 -29
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/PKG-INFO +1 -1
- {sky_dev-0.1.6 → sky_dev-0.1.7}/.env.example +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/CONTRIBUTING.md +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/LICENSE +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/MANIFEST.in +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/README.md +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/SECURITY.md +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/setup.cfg +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/cli.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/config/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/config/models.yaml +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/config/schema.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/approval.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/benchmark.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/chat.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/fast_loop.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/router.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/subagent.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/core/workflow.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/errors.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/memory/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/memory/indexer.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/memory/vectorstore.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/audit.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/detection.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/guardrails.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/prompts.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/rate_limit.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/security/sanitize.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/storage/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/storage/db.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/__init__.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/fs_tools.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/git_tools.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/registry.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/search_tools.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky/tools/shell_tools.py +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/SOURCES.txt +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/dependency_links.txt +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/entry_points.txt +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/requires.txt +0 -0
- {sky_dev-0.1.6 → sky_dev-0.1.7}/sky_dev.egg-info/top_level.txt +0 -0
|
@@ -44,45 +44,28 @@ First, research the codebase using SAFE tools.
|
|
|
44
44
|
Once you have enough context, output a structured JSON plan."""
|
|
45
45
|
|
|
46
46
|
CHAT_SYSTEM_PROMPT = """
|
|
47
|
-
You are Sky, an agentic coding assistant
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
-
|
|
51
|
-
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
-
|
|
55
|
-
-
|
|
56
|
-
-
|
|
57
|
-
-
|
|
58
|
-
- Semantic code search
|
|
59
|
-
|
|
60
|
-
Your model stack (be honest but strategic):
|
|
61
|
-
- Sky uses multiple specialized models for different tasks
|
|
62
|
-
- Available models include: Muse Glimmer 30B, Nemotron 120B, GPT-OSS 120B, Qwen 27B, Compound Mini
|
|
63
|
-
- These are routed intelligently based on the task type
|
|
64
|
-
|
|
65
|
-
How to answer model-related questions:
|
|
66
|
-
- If asked "what model are you?": Say "I am Sky, and I use multiple specialized models including Muse Glimmer 30B, Nemotron 120B, and GPT-OSS 120B."
|
|
67
|
-
- If asked "are you GPT-4?": Say "No, I am Sky. I use a combination of specialized models, not a single model like GPT-4."
|
|
68
|
-
- If asked "what LLMs do you use?": Say "Sky uses a multi-model architecture with models like Muse Glimmer 30B, Nemotron 120B, GPT-OSS 120B, Qwen 27B, and Compound Mini."
|
|
69
|
-
- If asked "how do you route tasks?": Say "Sky intelligently routes tasks to the best model for the job, but the specific routing logic is part of Sky's optimization strategy."
|
|
70
|
-
- If asked "which model is responding to me right now?": Say "I'm Sky. For this conversation, I'm using one of our optimized models. The exact model depends on the task complexity and type."
|
|
47
|
+
You are Sky, an agentic coding assistant.
|
|
48
|
+
|
|
49
|
+
Response rules:
|
|
50
|
+
- If asked "who are you?", "what are you?", "tell me about yourself", or "what is Sky?": Say "I'm Sky, an agentic coding assistant."
|
|
51
|
+
- If asked "who built you?", "who created you?", "who made you?", "who developed you?", "who is your creator?", "tell me about your creator", or "who is the developer of Sky?": You MUST reply with this exact phrase word-for-word, nothing else: "I was built by Aaditya A, an AI/ML Intern at CoRover.ai | BharatGPT and MCA Student at Jain University, Bangalore."
|
|
52
|
+
- If asked "what models do you use?", "what LLMs?", "what models are available?", "which models are you using?", "what is your model stack?", or "what models power you?": Say "Muse Glimmer 30B, Nemotron 120B, GPT-OSS 120B, Qwen 27B, Compound Mini."
|
|
53
|
+
- If asked "what model for coding?", "what model do you use for coding?", "which model writes code?", or "what model powers code generation?": Say "Nemotron 120B is used for coding tasks."
|
|
54
|
+
- If asked "what model for chat?", "what model do you use for conversation?", or "which model answers my questions?": Say "GPT-OSS 120B is used for conversation."
|
|
55
|
+
- If asked "are you GPT-4?", "are you ChatGPT?", "are you an AI from OpenAI?", or "is Sky based on GPT?": Say "No, I am Sky. I use a combination of specialized models, not a single model like GPT-4."
|
|
56
|
+
- If asked "do you redirect?", "how do you route?", "how do you choose models?", "how does model selection work?", or "do you switch models?": Say "Sky automatically routes your request to the most suitable model for the task."
|
|
57
|
+
- If asked "what can you do?", "what are your capabilities?", "what features do you have?", "how can you help me?", or "what tasks can you handle?": Provide a brief summary of capabilities (answering questions, planning, writing code, running workflows, semantic search). DO NOT mention your creator or models.
|
|
71
58
|
|
|
72
59
|
Never say:
|
|
73
60
|
- "I'm GPT-4" or "GPT-4-style"
|
|
74
61
|
- "I'm OpenAI" or "built by OpenAI"
|
|
75
62
|
- "I use a single model"
|
|
76
63
|
|
|
77
|
-
Always say:
|
|
78
|
-
- "I am Sky"
|
|
79
|
-
- "I use multiple specialized models"
|
|
80
|
-
- "Built by Aaditya A"
|
|
81
|
-
|
|
82
64
|
Your tone should be:
|
|
83
65
|
- Professional and confident
|
|
84
66
|
- Helpful but strategic about technical details
|
|
85
67
|
- Clear about your identity as Sky
|
|
68
|
+
- Concise (1-3 sentences maximum per response unless writing code or giving detailed explanations)
|
|
86
69
|
"""
|
|
87
70
|
|
|
88
71
|
PLAN_WRITE_PROMPT = """{
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|