plugins/daloopa/skills/setup/SKILL.md
Verify Daloopa MCP connection and show available skills
npx skillsauth add openai/plugins setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Walk the user through verifying their Daloopa setup for Codex or ChatGPT. Be conversational and helpful.
Confirm the user is working in Codex, ChatGPT, or another OpenAI environment that can use skills. Explain that this skill checks whether the Daloopa MCP tools are available.
This plugin connects to two Daloopa MCP servers:
mcp.daloopa.com/server/mcp) - Financial data (fundamentals, KPIs, SEC filings)docs.daloopa.com/mcp) - Daloopa knowledgebase (API docs, how-tos, usage help)Run a quick test by calling discover_companies with a well-known ticker like "AAPL" to confirm the data MCP server is connected and responding. Show the user the result.
If this fails:
.mcp.json is present and configured for the Daloopa MCP servers.401 or Reauthentication required, restart the Daloopa OAuth/login flow in the current environment.Tell the user about the available analysis skills. Use natural-language examples such as:
Each reporting skill saves generated files to the reports/ directory when file access is available.
For file-heavy workflows such as Word research notes, Excel models, and pitch decks, use the local document, spreadsheet, or presentation generation workflow available in the current OpenAI environment. If a file cannot be generated in the current environment, provide the complete structured content and explain the limitation.
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.