diegosouzapw/awesome-omni-skill / skills/ai-agents/add-backend-tool
add-backend-tool
VerifiedAdd a new tool to the backend OpenAI function calling system. Use when user mentions "new tool", "add tool", "backend function", "agent capability", or wants to extend what the AI agent can do.
Add Backend Tool
Instructions
-
Read
backend/main.pyto understand existing tool patterns:- Find the
toolslist with function definitions - Review helper functions (read_file, write_file, run_terminal_command, web_search)
- Find the
-
Create the helper function:
def new_tool_name(param1: str, param2: int = 10) -> str: """Docstring explaining the tool.""" try: # Implementation return result except Exception as e: return f"Error: {str(e)}" -
Add tool definition to the
toolslist:{ "type": "function", "function": { "name": "new_tool_name", "description": "What this tool does and when to use it", "parameters": { "type": "object", "properties": { "param1": {"type": "string", "description": "..."}, "param2": {"type": "integer", "description": "..."} }, "required": ["param1"] } } } -
Add tool invocation handler in the WebSocket message loop:
elif func_name == "new_tool_name": result = new_tool_name(**args) -
Update mode restrictions if needed:
- Agent mode: full access
- Chat mode: add to allowed list only if read-only/safe
Examples
- "Add a tool to list directory contents"
- "Create a tool for git operations"
- "Add web scraping capability"
Guardrails
- Include proper error handling with try/except
- Add timeout for any long-running operations
- Consider security implications (Chat mode restrictions)
- Never hardcode API keys or secrets
- Document the tool's purpose in the function docstring
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |