chore(agents): update skill metadata timestamps, source URLs, and documentation wording across dot_agents files

dot_agents/skills/linear-cli/SKILL.template.md

@@ -25,6 +25,70 @@ npx @schpet/linear-cli --version
 All subsequent commands can be prefixed with `npx @schpet/linear-cli` in place of `linear`. Otherwise, follow the install instructions at:\
 https://github.com/schpet/linear-cli?tab=readme-ov-file#install
 
+## Common Tasks
+
+Copy-pasteable recipes for the most frequent flows. Prefer these dedicated commands over `linear api` — reach for the GraphQL fallback only when no dedicated command or flag covers the operation.
+
+### Query issues with filters
+
+`issue query` searches across all assignees and supports structured filters that can be combined:
+
+```bash
+linear issue query --team ENG --state started --json
+linear issue query --project "Mobile App" --state backlog --state triage --unassigned
+linear issue query --assignee sam --label bug --updated-after 2026-01-01
+```
+
+Note: `linear issue list` is an alias of `issue mine` and only shows _your_ issues — use `issue query` for anything scoped to other people or a whole team/project.
+
+### List my issues
+
+```bash
+linear issue mine --state started --sort priority
+```
+
+### Create an issue
+
+```bash
+linear issue create --team ENG --title "Fix login redirect" \
+  --description-file ./description.md --no-interactive
+```
+
+Write multi-line markdown to a file and pass `--description-file` (see the markdown section below); `--no-interactive` avoids prompts in scripted use.
+
+### Update an issue's state, assignee, or labels
+
+```bash
+linear issue update ENG-123 --state "In Review" --assignee sam
+linear issue update ENG-123 --unassign
+linear issue update ENG-123 --add-label security             # add, keep existing labels
+linear issue update ENG-123 --remove-label sprint-42         # detach; does not delete the label
+linear issue update ENG-123 --remove-label sprint-42 --add-label sprint-43  # atomic swap
+linear issue update ENG-123 --label infra --label security   # replaces the label set
+```
+
+### Add a comment
+
+```bash
+linear issue comment add ENG-123 --body-file ./comment.md
+```
+
+### Attach an image or screenshot so it is visible inline
+
+```bash
+linear issue comment add ENG-123 --attach ./screenshot.png
+```
+
+This uploads the image and embeds it in a comment, where Linear renders it inline. Do not use `linear issue attach` when the image must be visible: that command creates a sidebar link attachment and does not render images inline.
+
+### View an issue / get its URL
+
+```bash
+linear issue view ENG-123          # details incl. comments
+linear issue view ENG-123 --json   # structured output
+linear issue url ENG-123           # print just the URL
+```
+
 ## Best Practices for Markdown Content
 
 When working with issue descriptions or comment bodies that contain markdown, **always prefer using file-based flags** instead of passing content as command-line arguments:
@@ -92,7 +156,7 @@ Each command has detailed help output describing all available flags and options
 
 Some commands have required flags that aren't obvious. Notable examples:
 
-- `issue list` requires a sort order — provide it via `--sort` (valid values: `manual`, `priority`), the `issue_sort` config option, or the `LINEAR_ISSUE_SORT` env var. Also requires `--team <key>` unless the team can be inferred from the directory — if unknown, run `linear team list` first.
+- `issue list` sorts by priority by default — override via `--sort` (valid values: `manual`, `priority`), the `issue_sort` config option, or the `LINEAR_ISSUE_SORT` env var. Requires `--team <key>` unless the team can be inferred from the directory — if unknown, run `linear team list` first.
 - `--no-pager` is only supported on `issue list` — passing it to other commands like `project list` will error.
 
 ## Using the Linear GraphQL API Directly