617 skills · sorted by relevance
Inspect and remove invisible characters from text and AI provenance metadata, information about content origin, from images and documents. It also supports prose rewriting and reports what changed, with limits on verifying watermark removal.
Document how a research or coding session evolved after the work is complete. The skill extracts decisions, experiments, failed approaches, and claims into ara/ files, distinguishing user statements from AI suggestions and actions.
Track exact provenance for every operation on ENCODE data — tool versions, reference files, scripts, parameters, and timestamps — to enable publication-ready methods writing. Use when the user processes ENCODE files, runs any bioinformatics tool, creates filtered/merged datasets, runs pipelines, performs liftover, uses R/Python/Bash for analysis, or needs to document their analysis chain for reproducibility and publication. Also use when the user says "write me methods" to auto-generate methods sections from the provenance log. This skill implements comprehensive provenance documentation: every tool, every version, every reference file, every parameter, every accession — no shortcuts. Use this skill for ANY processing step, ANY file transformation, ANY analysis operation on ENCODE data.
The English summary is being prepared. Showing the original description.
Check whether an OpenClaw release is fully available by comparing publication records, package provenance, test evidence, and live Gateway behavior against the requirements for its regular or extended-stable release track.
Record and inspect source history, trust scores, and handling labels on AI-generated or modified files. Use AKF metadata, information attached to files, to support review, handoff, and advisory audit checks without treating labels as proof of compliance.
Provider-independent provenance, rights, consent, disclosure, and release governance for AI-generated media. Use when producing or reviewing generated images, video, audio, ads, avatars, product content, social clips, documentaries, localization, music, sound, or campaign assets that need source-rights checks, model/provider term checks, likeness or voice consent, trademark/logo review, copyrighted-character/style risk triage, music licensing, C2PA/content credentials, provenance ledgers, release notes, platform disclosures, jurisdiction/client caveats, or rights QA.
The English summary is being prepared. Showing the original description.
AKF — The AI Native File Format workflow skill. Use this skill when the user needs The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
The English summary is being prepared. Showing the original description.
AKF — The AI Native File Format workflow skill. Use this skill when the user needs The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
The English summary is being prepared. Showing the original description.
Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.
The English summary is being prepared. Showing the original description.
Use when you need to know where a piece of reporting actually came from — the user gives an article URL and asks "where does this come from?", "who is the original source?", "is this just a rewrite?", or another skill needs the provenance chain before grading or citing a report. Follows an article's links and named attributions back to the originating vendor, government, victim or actor document and returns the chain, the primary's stated access and confidence language, publication dates, and every hop it could not resolve. Deterministic — a script or the Liberty91 platform resolves the chain; the model does not reconstruct it from memory. Invoked by /quality-of-information-check, /threat-actor-profiling, /campaign-tracking and /intelligence-writing. Works on any URL with no API key.
The English summary is being prepared. Showing the original description.
Sign and verify container image provenance using Sigstore Cosign with keyless OIDC-based signing, attestations, and Kubernetes admission enforcement.
The English summary is being prepared. Showing the original description.
Vendor (copy-import) a single external Claude Code skill into your own skills repo correctly — with license compliance and full provenance/attribution. Deterministic, idempotent primitive: given an upstream ref (owner/repo/path@sha or a GitHub URL) it fetches the skill, detects and gates on the license, copies the folder, injects a provenance frontmatter block (license + metadata: author/source/upstream_commit/vendored_at/provenance), ships the upstream LICENSE, adds a ## Credits section, and records a CREDITS.md ledger entry. Use when the user asks to "vendor a skill", "import a skill", "clone a skill", "borrow someone's skill", "add an external skill with attribution/credit", or スキルを取り込む / vendoring / 他人のスキルを自分のリポに取り込む. This is the import primitive that a skill-scout/curator orchestrator calls; it does NOT discover or evaluate — it correctly imports ONE skill you already chose.
The English summary is being prepared. Showing the original description.
Explore gene, drug, disease, and phenotype associations in a downloaded PrimeKG CSV. Retrieve direct relationships, disease summaries, and paths through one intermediate node while preserving relationship types and data provenance for reproducible research and hypothesis generation.
Look up biomedical relationships in ARAX using explicit entity types and tightly bounded paths. Inspect direct links or paths through one intermediate entity, along with returned publications and source records, to identify candidates for further research.
Store and retrieve execution output, model responses, reports, and operation receipts in YYLO Ledger. Choose storage and retention settings, attach provenance describing the source, and verify immutable evidence using record identifiers and content digests.
Find AAS skills for a stated task and compare their full instructions and supporting files before installation. Review each candidate’s fit, setup requirements, provenance, risks, and limitations using the bundled local catalog.
Guides review of pull requests from external forks, covering code ownership, contribution terms, security-sensitive changes, and tests tied to the reviewed commit. It produces a review record and supports moving changes to a maintainer branch when needed.
Apply staged improvements to skill files after explicit user selection and a fresh review by a different model family. Each applied change includes a backup, review records, and provenance details for later inspection.
Run repeatable, read-only checks on an Obsidian wiki to find broken or ambiguous links, isolated pages, missing metadata, empty sections, outdated index entries, and source-record issues. Review findings with paths, line numbers, and counts.
Record operations across multiple AI agents and connect events into a traceable history. Search records by tracking ID, time window, or responsible component to support audits and investigations, with local storage available when the vector database fails.
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
Removes and identifies AI watermarks and provenance marks in images and video the user generated or edited. Covers Gemini sparkles, SynthID, Microsoft InvisMark, Meta Content Seal, C2PA, EXIF/XMP/IPTC metadata, and Sora/Veo/Seedance/Doubao/Dola/Hailuo/Vidu/Kling and Wan labels. Use when the user wants to strip or clean AI watermarks and generation labels, or asks whether a file was AI-generated or carries AI provenance, even if they do not name remove-ai-watermarks. Do not use for stock-agency, marketplace, classifieds, or other third-party paid-asset watermarks.
The English summary is being prepared. Showing the original description.
Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and embedded content (attachments, macros), risk indicators (PDF JavaScript actions, encryption), and content digests. Evidence gathering, not verdicts: Tika reports what the file asserts and what parsing observed; it does not attribute authorship or validate signatures. Use for triaging suspicious files, provenance questions, e-discovery-style review, or "is this file what it claims to be."
The English summary is being prepared. Showing the original description.
QIIME2 command-line workflow for 16S/ITS amplicon analysis. Alternative to DADA2/phyloseq R workflow with built-in provenance tracking. Use when preferring CLI over R, needing reproducible provenance, or working within QIIME2 ecosystem.
The English summary is being prepared. Showing the original description.