agentleFS
ryanmacleanryanmaclean/skills/datadog-backup/SKILL.md

datadog-backup

Skill1 starsChanged 49 days agoMITView on GitHub

Backup and restore OpenCode skills to Datadog notebooks. Use when user mentions backup skills, datadog notebook, or restore skills.

  • Reads credentials
  • Sends data out

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to backup OpenCode skills to Datadog notebooks and restore them when needed.

    line 13
  2. Very specific:

    Bash: - Run curl commands, manage-notebooks.sh script

    line 16
  3. Distinctive:

    Read: - Read skill files

    line 17
  4. Distinctive:

    Write: - Create notebook content

    line 18
  5. Distinctive:

    WebFetch: - Check Datadog API docs if needed

    line 19
  6. Distinctive:

    Use the Datadog API to create notebooks containing skill content:

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Datadog Skill Backup Skill

Overview

Use this skill to backup OpenCode skills to Datadog notebooks and restore them when needed.

Tools Required

  • Bash - Run curl commands, manage-notebooks.sh script
  • Read - Read skill files
  • Write - Create notebook content
  • WebFetch - Check Datadog API docs if needed

Backup Skills to Notebooks

Step 1: List current skills

ls $HOME/rust-town/irclaw/.opencode/skills/

Step 2: Create notebook for each skill

Use the Datadog API to create notebooks containing skill content:

# Set credentials
export DD_API_KEY="your_api_key"
export DD_APP_KEY="your_app_key"

# Create notebook with skill content
SKILL_NAME="ansible-fleet"
SKILL_CONTENT=$(cat $HOME/rust-town/irclaw/.opencode/skills/${SKILL_NAME}/SKILL.md)

curl -s -X POST \
  -H "DD-API-KEY: ${DD_API_KEY}" \
  -H "DD-APPLICATION-KEY: ${DD_APP_KEY}" \
  -H "Content-Type: application/json" \
  -d "{
    \"data\": {
      \"type\": \"notebooks\",
      \"attributes\": {
        \"name\": \"Skill: ${SKILL_NAME}\",
        \"cells\": [
          {
            \"type\": \"markdown\",
            \"attributes\": {
              \"definition\": {
                \"text\": \"$(echo "$SKILL_CONTENT" | jq -Rs .)\"
              }
            }
          }
        ]
      }
    }
  }" \
  "https://api.datadoghq.com/api/v1/notebooks"

Step 3: List notebooks to verify

bash scripts/manage-notebooks.sh --action list

Restore Skills from Notebooks

Step 1: Get notebook content

NOTEBOOK_ID=12345
bash scripts/manage-notebooks.sh --action get --notebook-id $NOTEBOOK_ID

Step 2: Extract skill content and save

The markdown cell content can be extracted and saved to a SKILL.md file.

Reference

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.