Skip to content
TrustedSkillsbeta
Back to all skills

Effect Time Tracing Logging

Checked
mepuka·vlatest·devops·MIT

This skill logs detailed timestamps and effects associated with actions, aiding in debugging, analysis, and understanding complex processes.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add mepuka/effect-ontology --skill effect-time-tracing-logging -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

mepuka

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned mepuka/effect-ontology at c148102d57.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 97 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to record and analyze the timing of effects, providing detailed logs of when actions occur. It allows for tracing the sequence of events within an agent's execution, which is crucial for debugging complex behaviors or understanding system performance. The skill facilitates logging effect durations and dependencies.

When to use it

  • Debugging Complex Agent Behavior: Identify bottlenecks or unexpected delays in a chain of actions.
  • Performance Analysis: Measure the time taken by individual effects to optimize agent efficiency.
  • Understanding Dependencies: Visualize the order in which effects are triggered and their relationships.
  • Auditing Actions: Create a detailed record of all actions performed, useful for accountability or compliance.

Key capabilities

  • Effect Timing Recording
  • Dependency Tracing
  • Detailed Logging
  • Duration Measurement

Example prompts

  • "Log the duration of the 'move_to' effect."
  • "Trace the dependencies of the 'send_email' effect."
  • "Show me a timeline of all effects executed in the last 5 minutes."

Tips & gotchas

The skill requires access to the agent’s execution environment and may need specific permissions to log system events. Ensure that logging levels are appropriately configured to avoid excessive data generation.