AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Trace Behavior

skill-fikrilal-engineering-agent-skills-trace-behavior · by fikrilal

Trace one user action, background job, request, event, data mutation, or failure path end to end through a codebase. Use for questions such as how refresh works, where a setting is stored, what happens at startup, how authentication restores, or why an observed result appears. This skill is explanatory and read-only by default.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-fikrilal-engineering-agent-skills-trace-behavior

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fikrilal-engineering-agent-skills-trace-behavior)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Trace Behavior? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Trace Behavior

Follow real control flow and data flow across boundaries until the observable outcome is explained.

Workflow

  1. Restate the behavior as a concrete trigger and expected observable result.
  2. Read repository instructions, then locate the true entry point using search and call sites. Do not begin from a similarly named helper without confirming reachability.
  3. Follow control flow across UI, transport, application, domain, infrastructure, persistence, and external-process boundaries as applicable.
  4. Track important data alongside control flow: creation, validation, transformation, ownership, persistence, and presentation.
  5. Record branching, async handoffs, retries, cancellation, timeouts, caching, deduplication, and transaction boundaries when present.
  6. Trace failure or recovery only when it affects the requested behavior or explains an observed problem.
  7. Mark runtime behavior that static inspection cannot resolve.

Output

Default to this compact shape:

  1. In short: two or three sentences describing the trigger and result.
  2. Flow: a numbered runtime sequence with inline file references.
  3. Important detail: state ownership, persistence, async behavior, or failure handling only when needed.

For complex flows, include a compact text sequence diagram. Do not use a diagram when a short numbered sequence is clearer.

Explanation Rules

  • Ground each important step in reachable code, runtime composition, or configuration.
  • Explain ownership: which component decides, stores, transforms, or transports.
  • Use the learner's known concepts only when the analogy is structurally accurate.
  • Give the shortest complete trace first and expand on request.
  • State uncertainty only where static inspection cannot establish runtime behavior.

Guardrails

  • Do not modify files or runtime state.
  • Do not stop at interface declarations; find concrete composition and implementations.
  • Do not present inferred runtime behavior as confirmed.
  • Avoid unrelated architecture commentary; stay centered on the requested behavior.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.