← ClaudeAtlas

picsio-help-docslisted

Answer questions about how Pics.io itself works by reading the official Help Center at help.pics.io. Use for questions about Pics.io features, setup and settings — keywording and AI tagging, collections and lightboards, smart collections and saved searches, custom fields and metadata, version control, comments and approvals, websites and shared collections, inboxes, facial recognition, storage and sync with Google Drive / S3 / Dropbox, teammates and roles, billing and plans, integrations and the API. Use whenever someone asks "how do I…", "can Pics.io…", "where is the setting for…", "why does Pics.io…", or asks for documentation, a guide or a help article about Pics.io.
TopTechPhoto/picsio-mcp-plugin · ★ 7 · AI & Automation · score 76
Install: claude install-skill TopTechPhoto/picsio-mcp-plugin
# Answering from the Pics.io Help Center The official documentation lives at <https://help.pics.io/en/> (an Intercom Help Center, ~130 articles across ~15 sections). This skill is about **how the product works**. For **what is in a customer's library**, use the `picsio-asset-search` skill and the Pics.io MCP tools instead. ## Finding the right article The Help Center's own search box is client-rendered — fetching `help.pics.io/en/search?q=…` returns an empty shell, so don't rely on it. Use this order instead: 1. **Web search, scoped to the domain.** `site:help.pics.io <the user's words>` is the fastest route to the right article. 2. **The bundled index.** [`reference/article-index.md`](reference/article-index.md) lists every section and article URL from the site's sitemap. Scan it for a matching slug — the slugs are descriptive (`1269287-marking-assets-with-stars-flags-and-color-labels`). 3. **Live sitemap** when the index looks stale or a topic is missing: fetch `https://help.pics.io/sitemap.xml` and match slugs yourself. 4. **Section pages** to browse a whole area, e.g. `https://help.pics.io/en/collections/294997-keywords`. Then **fetch the article and read it**. The index titles are derived from URL slugs, not from real headings — never answer from a slug alone. ## Writing the answer - Answer from the article's actual wording. Give the concrete path through the UI — menu, panel, button — rather than a paraphrase of the feature name. - **Always link