Unverified50% confidenceFactExact time
In the Agent framework, a plugin usually refers to a set of capability packages that can be installed and uninstalled independently, and may include tool functions, interface entry points and configuration items; unlike Skill, which focuses on 'telling the Agent how to use tools', plugins lean more toward engineering encapsulation.
1
Sources
50%
Confidence
Long-term
Relevance
10/30/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedCoze's product architecture divides functionality into two major directions: Agent (intelligent body) and Projects.79% similarVerifiedThe naming, description, and parameter documentation of a tool are the key context for an Agent to decide when to call it, and can be understood as a form of prompt engineering.79% similarUnverifiedAs more developers deploy agents to production environments and allow them to dynamically load tools, the attack surface has expanded from the traditional application layer to the agent toolchain layer.79% similarUnverifiedThe cross-framework portability of the Ledger depends on the Agent framework providing Hook capabilities, with the remaining functionality implemented through contracts and tools, decoupled from the specific orchestration engine.78% similarVerifiedA typical Agent usually includes a planning module, a memory module, a tool-calling module, and an execution module.78% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1118420API
curl https://kongchang.com/api/v1/knowledge/claims/1118420MCP
get_claim(id=1118420)