Skip to content
TrustedSkillsbeta
Back to all skills

Devlog

Checked
maoruibin·vlatest·devops·MIT

The Devlog skill automatically generates concise development logs, streamlining documentation and improving project tracking for developers.

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 maoruibin/devlog --skill devlog -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

maoruibin

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 maoruibin/devlog at 99b4a639f1.

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

Manifest
SKILL.md
Scanned
4 files, 840 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, devlog, likely enables AI agents to interact with and potentially manage developer logs. While the source provides minimal detail, we can infer that it allows for some form of log access or processing. It's designed to be integrated into AI agent workflows to handle development-related data.

When to use it

  • Debugging Assistance: When troubleshooting a software issue and needing to quickly review recent log entries.
  • Automated Reporting: To automatically generate summaries of application behavior based on log analysis.
  • Incident Response: During an incident, to rapidly access relevant logs for investigation.
  • Performance Monitoring: For analyzing log data related to application performance metrics.

Key capabilities

  • Log Access (implied)
  • Log Processing (implied)
  • Integration with AI Agent Workflows

Example prompts

  • "Show me the last 100 lines of the server logs."
  • "Summarize any errors logged in the past hour."
  • "Find all log entries containing 'database connection failed'."

Tips & gotchas

The specific functionality and data format supported by this skill are not detailed. Successful use will likely depend on understanding how it integrates with your existing logging infrastructure.