Install
$ agentstack add skill-fikrilal-engineering-agent-skills-trace-behavior ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Trace Behavior
Follow real control flow and data flow across boundaries until the observable outcome is explained.
Workflow
- Restate the behavior as a concrete trigger and expected observable result.
- 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.
- Follow control flow across UI, transport, application, domain, infrastructure, persistence, and external-process boundaries as applicable.
- Track important data alongside control flow: creation, validation, transformation, ownership, persistence, and presentation.
- Record branching, async handoffs, retries, cancellation, timeouts, caching, deduplication, and transaction boundaries when present.
- Trace failure or recovery only when it affects the requested behavior or explains an observed problem.
- Mark runtime behavior that static inspection cannot resolve.
Output
Default to this compact shape:
- In short: two or three sentences describing the trigger and result.
- Flow: a numbered runtime sequence with inline file references.
- 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.
- Author: fikrilal
- Source: fikrilal/engineering-agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.