workspace-project-manager
Skill20 starsChanged 3 days agoMITView on GitHub
Управлять Пространствами LidFly и project-first памятью Workspace: проекты, provider entities, кампании, документы, решения, настройки, задачи и AI-автозапуски. Использовать для любой записи памяти или управления проектом с точным workspace_project_id.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- semantic-coreSkill
- seo-optimizerSkill
- serp-monitorSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- semantic-coreSkill
- seo-optimizerSkill
- serp-monitorSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- workspace-project-managerSkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 4 are distinctive, and 13 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
13
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use for projects, clients, memory, decisions, documents, settings, saved campaign context, tasks, reminders and scheduled AI checks.
- Distinctive: line 19
Before writing audits, documents, decisions, snapshots, settings, provider/campaign links or provider-scoped tasks:
- Very specific: line 21
If exact workspace_project_id is known, use it.
- Very specific: line 23
If resolved, write with returned workspace_project_id.
- Very specific: line 24
If ambiguous, show candidates and ask for exact workspace_project_id.
- Very specific: line 25
If no project matches, offer workspace_create_project.
- Very specific: line 32
Call top-level get_provider_context with the exact workspace_project_id before treating a missing provider scope as an error.
- Very specific: line 33
If it returns provider_link_candidates, those scopes are verified but not executable inside the project yet.
- Very specific: line 34
When the user asked to link the cabinet, choose the exact candidate and execute only its prepared next_action through call_write_tool.
- Very specific: line 35
If several candidates are returned, ask the user which cabinet to link.
- Distinctive: line 37
Read-only project members must not receive unlinked owner OAuth candidates.
- Very specific: line 63
Never pass top-level meta-tools such as search_tools or get_tool_schema as tool_name.
- Very specific: line 71
If can_delete=false, explain the returned blocker.
- Very specific: line 72
If ready, show confirmation_message, the deletion counts, and retained activity-history count.
- Very specific: line 73
Call workspace_delete_project through call_write_tool with the unchanged workspace_project_id, expected_project_name, and …
- Distinctive: line 74
If the target changed, run the preflight again and request a new confirmation.
- Very specific: line 79
If a future check must be shown to the owner, asks a question, or needs a new decision or confirmation, use workspace_add_tasks.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Workspace Project Manager
Use for projects, clients, memory, decisions, documents, settings, saved campaign context, tasks, reminders and scheduled AI checks.
Model
- Пространство is the user-facing memory container.
- Workspace project is a business, project, direction, or agency client.
workspace_project_idis the canonical id for memory writes.- Provider identifiers are external entities, not project ids:
client_login,client_id,account_id,counter_id,host_id,subdomain.
Project Scope
Before writing audits, documents, decisions, snapshots, settings, provider/campaign links or provider-scoped tasks:
- If exact
workspace_project_idis known, use it. - Otherwise call
workspace_prepare_project_scopewith all known selectors:project_name,provider,external_entity_key,external_campaign_id,client_login,vk_client_id,account_id,metrika_counter_id,lidfly_subdomain,host_id,campaign_name. - If resolved, write with returned
workspace_project_id. - If ambiguous, show candidates and ask for exact
workspace_project_id. - If no project matches, offer
workspace_create_project; never silently create "Основной проект". - Project resolution selects a destination, not write permission. Write only on the user’s request or under a memory workflow authorized for this exact operation. Never capture another client’s data, style or decisions.
For a business brief or campaign history, read this guide.
Provider Links
- Call top-level
get_provider_contextwith the exactworkspace_project_idbefore treating a missing provider scope as an error. - If it returns
provider_link_candidates, those scopes are verified but not executable inside the project yet. - When the user asked to link the cabinet, choose the exact candidate and execute only its prepared
next_actionthroughcall_write_tool. Keep its arguments unchanged; MCP confirmation is still required. - If several candidates are returned, ask the user which cabinet to link. Never invent
client_loginfrom the project/account name orexternal_entity_key. - A missing provider link is a normal confirmation-gated write workflow, not a support incident. Do not call
support_prepare_reportfor it. - Read-only project members must not receive unlinked owner OAuth candidates; do not try to recover them through personal scope enumeration.
Tools To Prefer
Find Workspace tools with search_tools({ provider: "workspace", ... }); read each schema with get_tool_schema before its first call.
Read through call_tool:
workspace_list_projectsworkspace_get_projectworkspace_prepare_project_scopeworkspace_prepare_project_deletionworkspace_get_settingsworkspace_get_tasksworkspace_get_scheduled_ai_tasks
Write through call_write_tool:
workspace_create_projectworkspace_delete_projectworkspace_upsert_provider_entityworkspace_link_campaignworkspace_update_settingsworkspace_add_tasksworkspace_schedule_ai_task
Never pass top-level meta-tools such as search_tools or get_tool_schema as tool_name.
Permanent Project Deletion
Permanent deletion is owner-only, irreversible, and never allowed in an AI autostart.
- Resolve and use the exact
workspace_project_id; never select a deletion target from a similar name. - Call read-only
workspace_prepare_project_deletion. - If
can_delete=false, explain the returned blocker. Archive an active project only if the user asked; protected accounting history means the project must remain archived. - If ready, show
confirmation_message, the deletion counts, and retained activity-history count. Wait for an explicit textual confirmation. - Call
workspace_delete_projectthroughcall_write_toolwith the unchangedworkspace_project_id,expected_project_name, andexpected_updated_atfrom that preflight. - If the target changed, run the preflight again and request a new confirmation. After a transport-uncertain delete, reread the exact project before considering any retry.
Reminders vs AI Autostarts
workspace_add_tasksis a manual reminder: it stores a prompt and due date, but the due date only triggers email and never runs AI or provider tools.- If a future check must be shown to the owner, asks a question, or needs a new decision or confirmation, use
workspace_add_tasks. workspace_schedule_ai_taskis an AI autostart: LidFly executes the saved plan automatically at the specified time without a new confirmation.- Objects, actions, values, and all conditional branches must be fully approved before using
workspace_schedule_ai_task.
For workspace_schedule_ai_task:
allowed_toolsmust list real domain tools for the future run, not v3 meta-tools.- Include
workspace_project_idfor provider/campaign tasks. - For write future runs, include concrete target items and a confirmed plan.
Output
Summarize the selected project, created object type, whether it runs automatically, next user action and unconfirmed details.
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.

