Skip to content
TrustedSkillsbeta
Back to all skills

Fumadocs Deploy

Checked
foreveryh·vlatest·devops

Automates deployment of Fumadocs documentation sites from Git repositories, streamlining updates and maintenance.

Repository

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 foreveryh/deeptoai-skills --skill fumadocs-deploy -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

foreveryh

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 foreveryh/deeptoai-skills at 5198b5e2c9.

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

Commit
5198b5e2c9
Manifest
skills/fumadocs/fumadocs-deploy/SKILL.md
Scanned
1 file, 371 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

The fumadocs-deploy skill automates the deployment of documentation using Fuma Docs. It allows you to generate and publish your project's documentation directly from source code comments, streamlining the process of keeping documentation up-to-date. This skill can handle complex projects with multiple files and dependencies, ensuring consistent formatting and versioning.

When to use it

  • Automated Documentation Updates: Regularly update project documentation without manual intervention.
  • New Project Onboarding: Quickly generate initial documentation for a new software project.
  • Internal Knowledge Base: Create and maintain an internal knowledge base from code comments.
  • Release Documentation: Automatically deploy updated documentation alongside software releases.

Key capabilities

  • Fuma Docs integration
  • Automated deployment
  • Documentation generation from source code comments
  • Support for complex projects

Example prompts

  • "Deploy the Fuma Docs documentation for my project."
  • "Generate and publish the latest version of my project's documentation using Fuma Docs."
  • “Update the documentation with changes in commit [commit hash]”

Tips & gotchas

  • Requires a working Fuma Docs installation and configuration.
  • Ensure your project’s code comments are formatted correctly for Fuma Docs parsing.