// Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.
Manage user profile including watchlists, portfolio, and preferences.
DCF valuation: free cash flow projections, WACC, terminal value, sensitivity analysis
Inline HTML widgets: charts, dashboards, data tables rendered directly in the chat via ShowWidget
Web scraping with Scrapling: MCP tool wrappers for quick fetching, plus direct Python API for advanced scraping with selectors, sessions, and spiders
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Search X (Twitter) posts, pull user profiles, fetch specific tweets, and read reply threads for sentiment, news, and event research. Triggers on 'X', 'Twitter', 'tweets about', 'sentiment on', 'what are people saying about', 'historical tweets', or any request to read public X content.
| name | secretary |
| description | Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads. |
Workflow patterns and operational details for the secretary tools. Basic tool signatures are in the tool descriptions — this covers what they don't.
These actions pause for user confirmation before executing:
manage_workspaces(action="create"|"delete"|"stop")ptc_agent(...) — always, before dispatchmanage_threads(action="delete")These run immediately (no approval):
manage_workspaces(action="list")manage_threads(action="list"|"get_output")agent_output(...)ptc_agent is asynchronous — it dispatches the question and returns immediately. The PTC agent runs in the background with full code execution, charts, and financial data tools.
Return: { success, workspace_id, thread_id, status: "dispatched", report_back }
workspace_id → auto-creates a new workspace (blocks ~8-10s for sandbox init)workspace_id → dispatches to existing workspace (new thread)thread_id → continues an existing conversation (overrides workspace_id)report_back=True (default) → when PTC completes, you'll automatically receive the results and should summarize them for the userreport_back=False → fire-and-forget; the user will check results in the workspace themselvesUse the returned thread_id with agent_output to check progress later (only needed when report_back=False).
Return: { text, status, thread_id, workspace_id }
status: "running" — analysis still in progress, text is partialstatus: "completed" — full output availablestatus: "error" — something went wrongWhen the user asks for a status overview, combine workspace and thread information:
manage_workspaces(action="list") to get workspace statesmanage_threads(action="list") to get recent thread activityptc_agent(question="...")agent_output(thread_id="...")When the user wants to follow up on a prior dispatch:
ptc_agent(question="...", thread_id="...") with the original thread_idWhen the user wants to tidy up:
manage_workspaces(action="list") to identify stale workspacesmanage_workspaces(action="stop", workspace_id="...")manage_workspaces(action="delete", workspace_id="...")