ByronScottJonesByronScottJones/Agents/skills/twg-artifacts/SKILL.md

twg-artifacts

Skill7 starsChanged 2 months agoMITView on GitHub

Use with root `twg` when a user wants to share, publish, send, or update a standalone local or generated file as an Atlassian Artifact. Do not use for Jira or Confluence attachments.

In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-pr-commentsSkill
- build-and-scan-container-imageSkill
- execute-database-migrationSkill
- generate-adrSkill
- generate-service-documentationSkill
- get-pr-commentsSkill
- incident-triageSkill
- install-dev-toolsSkill
- prepare-releaseSkill
- remediate-dependency-vulnerabilitiesSkill
- review-configurationSkill
- twg-agentic-searchSkill
- twg-code-reviewSkill
- twg-confluenceSkill
- twg-context-discoverySkill
- twg-engineering-workSkill
- twg-jira-resolve-merged-workSkill
- twg-jiraSkill
- twg-operational-healthSkill
- twg-responsibility-routingSkill
- twgSkill
- twg-space-creationSkill
- twg-status-rollupsSkill
- validate-and-deploy-iacSkill
- validate-and-deploy-kubernetesSkill
- validate-documentationSkill
- validate-github-actionsSkill
- verify-service-healthSkill

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 2 are distinctive, and 8 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Run twg <command>. On shell command not found, use $HOME/.local/bin/twg (macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe …
line 13
Very specific:
Use twg artifacts file create <path> when the user wants to share a standalone local or generated file with coworkers, such as a generated …
line 18
Very specific:
Use --access private when the user has not had a chance to review a generated file.
line 51
Very specific:
Use --access open when the user has reviewed the generated file, or supplied the existing file for sharing.
line 53
Very specific:
If it is unclear whether the user reviewed the file, use --access private.
line 56
Distinctive:
If the user explicitly wants the file attached to a Jira work item or Confluence page, use that product's attachment commands instead.
line 58
Very specific:
Use twg artifacts file get <artifact-id> only to retrieve metadata for an existing artifact.
line 61
Very specific:
Use twg artifacts file share <artifact-id> --account-id <account-id> to grant specific users access to an existing private artifact.
line 64
Distinctive:
If the artifact is open or shared, change it to private before adding explicit user grants.
line 68
Very specific:
Use twg artifacts file update <artifact-id> [path] to change an existing artifact.
line 81

≈ “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

TWG artifacts

CLI launcher fallback

Run twg <command>. On shell command not found, use $HOME/.local/bin/twg (macOS/Linux) / $env:LOCALAPPDATA\Programs\twg\bin\twg.exe (PowerShell), then tell user to add that directory to PATH. Do not treat auth or command errors as PATH failures.

Use twg artifacts file create <path> when the user wants to share a standalone local or generated file with coworkers, such as a generated HTML report, Markdown document, or presentation. Return the created artifact URL and metadata.

Thumbnail

Pass --thumbnail <png-path> on create or update when a representative preview is available. On macOS, an agent can generate one from the artifact file with qlmanage -t -s 512 -o <output-directory> <artifact-file>, then pass the generated PNG to --thumbnail.

HTML files

Upload only self-contained HTML. Embed the JavaScript, stylesheets, images, and other required assets in the file; it cannot depend on local files such as ./app.js. Avoid browser-storage APIs such as localStorage, sessionStorage, and IndexedDB: the artifact viewer's content security policy may restrict them.

Describe the content for search

Pass --description <text> with a concise summary of the file's actual content. This description is indexed to improve artifact search. When the user does not provide one, derive it from the content you created or inspected—not only from its filename or media type. Do not invent content you have not read.

Choose access for creation

<!-- Intentional: `open` is link-only within the organisation, whereas `shared`
makes an artifact discoverable. Artifacts are created to share with others, so
only unreviewed drafts stay private. -->

Use --access private when the user has not had a chance to review a generated file. This is also the CLI default.
Use --access open when the user has reviewed the generated file, or supplied the existing file for sharing. Pass it explicitly because the CLI default is private.
If it is unclear whether the user reviewed the file, use --access private.

If the user explicitly wants the file attached to a Jira work item or Confluence page, use that product's attachment commands instead.

Use twg artifacts file get <artifact-id> only to retrieve metadata for an existing artifact.

Use twg artifacts file share <artifact-id> --account-id <account-id> to grant specific users access to an existing private artifact. Repeat --account-id or pass a comma-separated list. The command accepts Atlassian account IDs and full ari:cloud:identity::user/... ARIs and validates them before changing access. If the artifact is open or shared, change it to private before adding explicit user grants.

Use twg artifacts file unshare <artifact-id> --account-id <account-id> to revoke named user grants, or --all to revoke every explicit audience grant, including users, groups, and teams. Revocation does not change the artifact's general access. Named account IDs are validated before access changes are made. The validation checks the artifact's current explicit grants, so a grant can be removed even when the user's profile is hidden or the account is closed. It requires confirmation; pass --yes in agent mode or only after the user has approved the complete resolved audience set. --all is never inferred from an empty user list.

Use twg artifacts file update <artifact-id> [path] to change an existing artifact. Pass a replacement file path to publish new content; omit it to change metadata such as the name, description, or access. For a content update, derive --description from the replacement file's actual content when the user has not provided one. Omit --access unless the user explicitly asks to change visibility; an update otherwise preserves the artifact's existing access.

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.

Check your setup, free