Action trace
A record of actions proposed or invoked during a workflow. It should be correlated with verified effects.
Explore this concept ↗55 concise definitions, each linked to a guide that explains its relevance to reusable agent skills.
A record of actions proposed or invoked during a workflow. It should be correlated with verified effects.
Explore this concept ↗The decision process for allowing a package into an approved environment under a defined scope.
Explore this concept ↗A reusable package of task guidance and optional resources that extends an agent’s workflow.
Explore this concept ↗The share of evaluated cases meeting a study’s definition of successful attack. It depends on the denominator and configuration.
Explore this concept ↗An enforced limit on data access or actions available to a package-driven workflow.
Explore this concept ↗Hidden behavior that activates under particular conditions while a component may otherwise behave normally.
Explore this concept ↗Checking observed actions or effects rather than inferring behavior from text alone.
Explore this concept ↗Executable code distributed with a skill and used by its workflow.
Explore this concept ↗A synthetic marker used in an isolated test to observe access or movement without exposing a real secret.
Explore this concept ↗A record tying a statement to its source version, conditions, and verification limits.
Explore this concept ↗Runtime limits on reachable files, networks, processes, or actions to restrict the effects of unsafe behavior.
Explore this concept ↗A record of expected artifacts and which were fully, partially, or unsuccessfully inspected.
Explore this concept ↗A file or record that persists after one agent session and influences a later skill run.
Explore this concept ↗A skill or revision produced from an earlier record or component.
Explore this concept ↗The transition where an example or template influences an executable artifact or action.
Explore this concept ↗A package that may complete the visible task while performing an additional unauthorized action.
Explore this concept ↗A label describing how directly a finding is supported, according to a tool’s stated criteria.
Explore this concept ↗The process that turns task histories into persistent reusable procedures.
Explore this concept ↗A malicious or unsafe case that a detector fails to flag under its stated criteria.
Explore this concept ↗A benign case incorrectly flagged or blocked by a detector or policy.
Explore this concept ↗An explicit description of the data and validation expected between two workflow components.
Explore this concept ↗A transition where an agent asks a person to perform an action outside the agent’s enforced environment.
Explore this concept ↗An instruction-manipulation attempt arriving through content the agent reads, such as a skill reference, instead of the direct user request.
Explore this concept ↗The distinction between task guidance a source may provide and actions it is authorized to request.
Explore this concept ↗Whether an artifact matches a recorded state. Matching bytes do not prove safe behavior.
Explore this concept ↗A file or record passed between stages or skills; its source can matter to the final action.
Explore this concept ↗Granting only the capabilities and access required for an approved use case.
Explore this concept ↗Misleading or malicious discovery content that influences how a skill is found, selected, or interpreted.
Explore this concept ↗A skill that includes a learned model artifact as part of its logic.
Explore this concept ↗Supporting content that can change independently of the installed skill revision.
Explore this concept ↗The time period covered by collection or analysis, which may differ from publication date.
Explore this concept ↗An explicit statement of the criteria and constraints a generated result must satisfy.
Explore this concept ↗Whether the result follows the user’s authorized criteria, sources, and recipients.
Explore this concept ↗A test beginning after a skill has loaded; it does not by itself evaluate discovery or installation.
Explore this concept ↗A method that screens material before it runs; a positive result is not evidence of completed impact.
Explore this concept ↗A research manuscript shared before or separately from a final peer-reviewed publication.
Explore this concept ↗A setup claim used to make a legitimate task conditional on an unverified or unrelated installation.
Explore this concept ↗Context presented as the reason a later skill should act; review its origin and integrity.
Explore this concept ↗Loading metadata, instructions, and supporting resources as they are needed, rather than exposing the entire package at once.
Explore this concept ↗Evidence of where a package or artifact came from and how it reached the reviewed environment.
Explore this concept ↗Removing a package’s availability or access after approval is withdrawn.
Explore this concept ↗Returning artifacts or configuration to a previously reviewed state; external effects may need separate recovery.
Explore this concept ↗The entry file used by the Agent Skills format for metadata and Markdown instructions.
Explore this concept ↗Using multiple skills or their outputs together in a workflow.
Explore this concept ↗Producing a reusable procedure from examples or completed interactions.
Explore this concept ↗Malicious instructions or behavior introduced through a reusable skill or its supply chain. A working umbrella in this library.
Explore this concept ↗Testing on sources held out from training or tuning to probe source-dependent generalization.
Explore this concept ↗A group of closely related artifacts considered together when controlling evaluation overlap.
Explore this concept ↗A condition associated with activating hidden behavior in a backdoored component.
Explore this concept ↗Inspection limited to part of an artifact; the unprocessed remainder remains outside the finding.
Explore this concept ↗The extent to which a system completes legitimate tasks in the evaluated conditions.
Explore this concept ↗Identifying and retaining the exact package or dependency state approved for a workflow.
Explore this concept ↗No matching terms.