← ClaudeAtlas

manage-vklisted

Work with VK (VKontakte) from an agent - read a community before writing to it, publish a post or photos to a wall, and tell a refusal from an empty answer. Covers the community access token and the places it must never travel, the confirmation gate that stands before anything is published, the rate ceiling, the photo upload sequence, and the error codes that look like success because VK answers HTTP 200 with the failure in the body. Ships a read-only preflight that must pass before the first write, and a Russian typography linter with the range rule narrowed so it cannot corrupt ГОСТ or telephone numbers. Use when the user asks to post to VK, to check a VK community, to read a VK wall, when a VK API call returns a surprising result, when a token has to be configured, or when Russian text is being prepared for VK.
ubik-dsh/deepseek-harness-skills · ★ 0 · AI & Automation · score 63
Install: claude install-skill ubik-dsh/deepseek-harness-skills
# Working with VK from an agent VK is not hard to call. It is easy to call **wrongly and be told you succeeded**, which is why this skill is mostly about what happens before and after the request. ## The order to think in: boundaries, functions, meaning, requests **A request is the last thing to think about, not the first.** Work down these four layers, and each is only useful once the one beneath it is settled. ``` 1 boundaries what this credential can touch at all 2 functions the exact calls, their parameters and their returns 3 meaning what each call does to the community, and which calls compose into a capability 4 requests a sentence from a person becomes a sequence, or a refusal ``` **A skill that starts at the request answers some requests and fails on the rest, and never knows which.** «Запость на стену погоду в Лобне» is a one-line request whose difficulty is in layers 3 and 4 and almost not at all in layer 2 — publishing is one call. What the request leaves out is the source, the time, the units, the meaning of the numbers the source returns, what to do when the source is down, and what to do about a table VK will delete. **Layer 3 is the one this family keeps skipping**, and the failure it causes is quiet: a function is documented and a capability is assumed. `wall.post` is a function; *publish something that cannot be taken back* is the capability, and only the second one is what the person asked for. [references/capabilities.md](reference