Doc Sync
CheckedDoc Sync seamlessly synchronizes documents across different platforms, streamlining workflows and ensuring everyone works with the latest version.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add akiselev/qt-llm-template --skill doc-sync -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
akiselev
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.
Automated safety checks
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 akiselev/qt-llm-template at 6855e82e0c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 6855e82e0c
- Manifest
- .claude/skills/doc-sync/SKILL.md
- Scanned
- 5 files, 405 lines
About this skill
What it does
The doc-sync skill synchronizes documentation files between a local directory and a remote repository. It supports both pushing changes from your local machine to the remote repository, as well as pulling updates from the remote repository to keep your local copy synchronized. This ensures that your documentation remains consistent across different environments.
When to use it
- Updating project documentation: When you've made changes to your project’s documentation and need to push those changes to a central repository for sharing or version control.
- Keeping local copies up-to-date: To ensure your local documentation reflects the latest updates from a shared team repository.
- Automating documentation deployment: As part of a CI/CD pipeline, automatically synchronize documentation updates whenever code is merged.
- Collaborative documentation editing: Facilitate real-time collaboration by ensuring all contributors have access to the most current version of the documentation.
Key capabilities
- Pushing local changes to a remote repository
- Pulling changes from a remote repository
- Synchronization of documentation files
Example prompts
- "Sync my local documentation to the
mainbranch on GitHub." - "Pull the latest updates for the documentation from the remote repository."
- "Update all markdown files in the
/docsdirectory with the changes from the online repository."
Tips & gotchas
The skill requires access credentials (e.g., SSH keys or API tokens) to interact with the remote repository. Ensure these are properly configured before attempting synchronization.