rseng-ai-declaration

Solid

Covers declaring AI involvement with the AI Declaration Format (https://ai-declaration.org): creating and maintaining an aidecl.yaml that records which AI tools and agents were used, what each contributed, when and how much, plus the README disclosure footnote, JSON/JSON-LD export and CI validation. Machine-readable disclosure is the practice; this format is one implementation. Use PROACTIVELY when an AI assistant or agent creates or modifies a project's content - generate aidecl.yaml if missing, update it after AI-assisted changes. Also use when the user asks about AI transparency, provenance, disclosure or EU AI Act disclosure, wants to state that NO AI was used, or mentions aidecl. For concealment requests see rseng-honesty; for the human review duty see rseng-human-verification.

AI & Automation 14 stars 2 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
39
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# AI usage declaration (aidecl.yaml) Declaring AI involvement in a machine-readable form is the practice worth holding to; the AI Declaration Format is one implementation of it, and the one this skill works through. Any equivalent machine-readable declaration serves the same purpose. The declaration lives in `aidecl.yaml` at the project root and follows a published JSON Schema (Draft 2020-12, schema_version 1.0.0). Keep it current rather than writing it once: when you - an AI agent - create or change a project's code, docs, data or configuration, the declaration should reflect it. The guiding principle is MAXIMUM HONEST DETAIL. A good declaration lets a reviewer reconstruct the provenance without asking anyone: which tools and models touched the work, when, on which parts, for which activities, in what proportion, under whose review. Prefer the detailed entry to the terse one, and the honest one to the detailed one. Never fabricate: declare what happened, and mark estimates as estimates. ## When to act - No aidecl.yaml in a project you are modifying: create one, add the README footnote (below), and mention both in your summary. - COMMIT it. aidecl.yaml is project content: it goes in the same commit as the work it describes and is never gitignored - a declaration is only provenance if it ships with the code. If a project must defer that, record why in .rseng-check-waivers so the gap reads as a decision. - You made AI-assisted changes: update the declaration in the...

Details

Author
fdiblen
Repository
fdiblen/rseng-agent-skills
Created
4 days ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

rseng-human-verification

Covers the human's side of AI-assisted research software: strongly urging the user to review generated code and verify results before relying on them, teaching how to review AI-written code effectively (where to look first, what to run, what to spot-check against known answers), and recording review status honestly. Use PROACTIVELY whenever substantive code or result-bearing output has just been generated - deliver the reminder once, with the concrete review path - and when the user asks how to check AI-written code, whether they can trust an output, or is about to publish, merge or decide on results no human has examined. Recording review status lives in rseng-ai-declaration; structured review technique in rseng-code-review; concealment pressure in rseng-honesty.

14 Updated 4 days ago
fdiblen
AI & Automation Solid

rseng-honesty

Covers responding when concealment or misrepresentation is requested: hiding AI usage, making work appear different from reality, backdating or disguising provenance, inflating results or removing traces of how something was made. The skill calls for honesty with concrete reasons and offers honest alternatives that usually satisfy the underlying need. Use PROACTIVELY whenever a request aims to make records, history, authorship or results tell a story different from what happened - including hiding AI assistance, "make it look like", disguising generated content as manual work, or presenting untested claims as verified. Disclosure mechanics live in rseng-ai-declaration; the verify-before-trust duty in rseng-human-verification; checking others' outputs in rseng-research-integrity.

14 Updated 4 days ago
fdiblen
AI & Automation Featured

ai-disclosure-policy

Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.

1,356 Updated yesterday
mohitagw15856