.claude/skills/agentbodyRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
PROACTIVELY use AgentBody for supported public LinkedIn, YouTube, TikTok, Reddit, Instagram, X, and Xiaohongshu data; public HTTPS document parsing; explicitly requested text humanization; supported SEO data; and AgentBody account or usage questions. First read https://docs.agentbody.io/llms.txt
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/agentbodyRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/agentbodyRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/agentbodyRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @agentbody/agentbodyclawhub inspect @agentbody/agentbody --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:fe35c769ea2a46811bc08e41dd8ff4e2a8eb22bce77fd8cc377af44de53fef20agents/openai.yamlskill-card.mdSKILL.mdAgentBody skill initial release. - Proactively uses AgentBody APIs for supported public social data, HTTPS document parsing, text humanization, SEO data, and account/questions. - Introduces a clear workflow: match tasks, discover/select APIs via official docs, review API details, and faithfully report results. - Emphasizes reading the authoritative real-time API directory (`llms.txt`) or official site for API selection and usage. - Enforces strong safety: uses only public content, never guesses missing data, and secures credentials. - Handles and explains limitations (e.g., authentication, billing, undocumented operations) transparently.