atlas-crew-tasks

Included with Lifetime

$97 forever

Use when filing, updating, sequencing, or querying tasks in any atlas-crew repo (Facet + the Atlas Crew Security repos: Apparatus, Chimera, Crucible, Synapse, Bridge). These repos track work in GitHub Issues on Projects v2 boards, NOT backlog.md. Covers the two boards, the Type/Area/Status field model, cross-repo Initiative grouping, gh seq execution ordering, and the non-obvious gh/GraphQL mechanics for setting issue types and project fields. Trigger on: file an issue, create a task, set priority/type/area/status, add to board, what should I work on next, execution order, sequencing, blocked-by, milestone, where does this task go.

Backend & APIs

What this skill does


# Atlas Crew Task Tracking

Work for these repos lives in **GitHub Issues** on **Projects v2** boards, not
backlog.md. (A repo's `backlog/` directory is a frozen archive of completed
pre-migration work — read-only.)

## The two boards

| Board | Repos | URL |
| --- | --- | --- |
| **#8 Atlas Crew Security** (shared) | Apparatus, Chimera, Crucible, Synapse, Bridge | `https://github.com/orgs/atlas-crew/projects/8` |
| **#9 Facet** (standalone) | Facet | `https://github.com/orgs/atlas-crew/projects/9` |

Both are **org-owned** by `atlas-crew`. Always pass `--owner atlas-crew`.

## Classification model (three orthogonal axes)

Keep these separate — do not encode type or area as a label.

- **Type** → GitHub **Issue Type** (org-owned, shared by every repo):
  `Feature`, `Bug`, `Task`, `Chore` (refactor/tech-debt/maintenance),
  `Spike` (time-boxed investigation).
- **Area** → an **Area** single-select project field. *Facet #9 only* so far
  (Identity, Pipeline, Prep, Letters, Research, Build/Resume, Debrief,
  AI/Proxy, UI/Design System, Persistence, Testing/Infra, Docs, Cross-cutting).
  Board #8 has no Area field yet.
- **Concern** → **labels**: `accessibility`, `security`, `ux`, `cross-cutting`,
  `testing`, `documentation`, `playwright`, plus GitHub/dependabot conventions.

**Cross-repo grouping** is the **Initiative** single-select on board #8 (e.g.
"Platform Hardening", "Vuln Content") — use it for milestones that span ACS
repos. Within a single repo, use native GitHub **milestones**.

**Status** differs per board:
- #9 Facet: `Backlog → Todo → In Progress → Blocked → Done`.
- #8 ACS: `Todo → In Progress → Done` (not yet refined).

## Filing a task

```sh
# 1. create the issue (type can be set at creation via REST; see gotcha below)
gh issue create --repo atlas-crew/Facet --title "..." --body "..." --label ux

# 2. add it to the board
gh project item-add 9 --owner atlas-crew --url <issue-url>

# 3. set Type (see gotcha), then set project fields (Priority/Area/Status)
```

## Sequencing — what to work on next

Execution order is **not** a board field. It is derived from native issue
dependencies (`blocked-by`) + sub-issues, reconstructed into waves by `gh seq`:

```sh
gh seq --repo atlas-crew/Facet --order-by Priority      # single repo
gh seq --project 8 --owner atlas-crew --order-by Priority # whole ACS board
```

The GitHub UI cannot render topological order; `gh seq` is the canonical
"what can I start now" view. Set Status to **Blocked** on issues waiting in the
dependency graph (Facet #9).

## Mechanical gotchas (the parts that waste time if rediscovered)

**Setting an Issue Type — `gh issue edit` has NO `--type` flag.** Use the REST
issues endpoint, which takes the type name directly:
```sh
gh api -X PATCH /repos/atlas-crew/Facet/issues/13 -f type=Feature
```

**Creating a new org Issue Type needs the `admin:org` scope:**
```sh
gh auth refresh -h github.com -s admin:org
gh api -X POST /orgs/atlas-crew/issue-types -f name=Chore -F is_enabled=true \
  -f color=gray -f description="..."
```

**Setting a project single-select field (Priority/Area/Status) needs three
IDs** — project, field, option — and the item's id. Look them up; never
hardcode (they drift):
```sh
# field + option ids:
gh project field-list 9 --owner atlas-crew --format json
# item ids (maps issue number -> item id):
gh project item-list 9 --owner atlas-crew --format json
# then:
gh api graphql -f query='mutation{updateProjectV2ItemFieldValue(input:{
  projectId:"<PID>", itemId:"<ITEM>", fieldId:"<FIELD>",
  value:{singleSelectOptionId:"<OPTION>"}}){projectV2Item{id}}}'
```

**Editing single-select options (e.g. adding a Status value) — preserve
existing option IDs.** `ProjectV2SingleSelectFieldOptionInput` accepts `id`;
re-send existing options *with their id* and append new ones, or you detach
every item's current assignment.

**Views cannot be created via API** — there is no `createProjectV2View`
mutation. View setup is manual in the board UI.

## Reference

Each repo's board conventions and view configs:
`docs/development/project-board.md` (Facet has one; mirror it per repo as the
ACS board gains fields).

Files: 1

Size: 4.9 KB

Complexity: 19/100

Category: Backend & APIs

Source: https://github.com/nickcrew/claude-cortex/tree/main/skills/atlas-crew-tasks

Related in Backend & APIs

jfrog

Included

Interact with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.

Backend & APIsscripts

cupynumeric-migration-readiness

Included

Pre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.

Backend & APIsscripts

alibabacloud-data-agent-skill

Included

Invoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".

Backend & APIsscripts

token-optimizer

Included

Reduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.

Backend & APIsscripts

resend-cli

Included

Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.

Backend & APIsscripts

alibabacloud-odps-maxframe-coding

Included

Use this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.

Backend & APIsscripts