AI Skills Documentation#241
Open
Logan-Huang wants to merge 3 commits into
Open
Conversation
May have to produce an updated workflow documentation with the steps for Claude such as /plan, etc...
Given example of local galaxy cluster database
Removed redundancy and added some notes from personal experience
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #241 +/- ##
==========================================
- Coverage 72.38% 68.97% -3.41%
==========================================
Files 19 19
Lines 1673 1673
Branches 211 211
==========================================
- Hits 1211 1154 -57
- Misses 380 441 +61
+ Partials 82 78 -4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
kelle
requested changes
Jun 2, 2026
Contributor
kelle
left a comment
kelle
left a comment
There was a problem hiding this comment.
also add Claude as a co-author.
Comment on lines
+18
to
+19
| These skills only apply to the local repository you're running the agent from. | ||
| For skills to be available globally, copy them into ``%USERPROFILE%/.claude/skills/`` or the equivalent for your agent. |
Contributor
There was a problem hiding this comment.
Suggested change
| These skills only apply to the local repository you're running the agent from. | |
| For skills to be available globally, copy them into ``%USERPROFILE%/.claude/skills/`` or the equivalent for your agent. |
| The skills are designed to run in sequence, each feeding the next, but any of them can | ||
| also be run on its own. | ||
|
|
||
| #. **astrodb-parse-data-table** — Reads a data table (FITS, CSV, ECSV, HDF5, VOTable, |
Comment on lines
+68
to
+82
| Example: Building From The Local Group Galaxy Database | ||
| ----------------------------------------------- | ||
| The following condensed walkthrough shows the skills used end to end in a real | ||
| Claude Code session that built a database from McConnachie's *Nearby Galaxies* | ||
| catalog (``NearbyGalaxies_Jan2021_PUBLIC.fits`` — 144 Local Group dwarf galaxies). | ||
|
|
||
| **Setting up the session.** A few Claude Code slash commands configured the run | ||
| before any work began: | ||
|
|
||
| .. code-block:: text | ||
|
|
||
| /effort ultracode # maximum reasoning effort + dynamic workflow orchestration | ||
| /model # Opus 4.8 (1M context) | ||
| /advisor # route review checkpoints to a second Opus 4.8 reviewer | ||
| /plan # enter plan mode to scope the whole build before any changes |
Contributor
There was a problem hiding this comment.
Suggested change
| Example: Building From The Local Group Galaxy Database | |
| ----------------------------------------------- | |
| The following condensed walkthrough shows the skills used end to end in a real | |
| Claude Code session that built a database from McConnachie's *Nearby Galaxies* | |
| catalog (``NearbyGalaxies_Jan2021_PUBLIC.fits`` — 144 Local Group dwarf galaxies). | |
| **Setting up the session.** A few Claude Code slash commands configured the run | |
| before any work began: | |
| .. code-block:: text | |
| /effort ultracode # maximum reasoning effort + dynamic workflow orchestration | |
| /model # Opus 4.8 (1M context) | |
| /advisor # route review checkpoints to a second Opus 4.8 reviewer | |
| /plan # enter plan mode to scope the whole build before any changes | |
| Example and Prompt Advice | |
| ----------------------------------------------- | |
| We recommend using plan mode. |
|
|
||
| The ``/plan`` prompt was *"Review your astro-db skills and create a plan to | ||
| have a fully working database after going through @NearbyGalaxies_Jan2021_PUBLIC.fits"*. | ||
| Plan mode let the agent inspect the FITS file and propose a complete build plan for |
Contributor
There was a problem hiding this comment.
Suggested change
| Plan mode let the agent inspect the FITS file and propose a complete build plan for | |
| Plan mode tells the agent to inspect the FITS file and propose a complete build plan using all of the available skills for |
Contributor
There was a problem hiding this comment.
You could alternatively run each skill one-by-one.
Contributor
There was a problem hiding this comment.
Add that the output of this prompt is a populated SQLite database based on the data in the input file.
| /advisor # route review checkpoints to a second Opus 4.8 reviewer | ||
| /plan # enter plan mode to scope the whole build before any changes | ||
|
|
||
| The ``/plan`` prompt was *"Review your astro-db skills and create a plan to |
Contributor
There was a problem hiding this comment.
make the prompt stand out more.
Comment on lines
+90
to
+103
| **Running the pipeline.** With the plan approved, the skills ran in sequence, each | ||
| feeding the next: | ||
|
|
||
| #. **astrodb-parse-data-table** — parsed all 50 columns (names, units, descriptions). | ||
| #. **astrodb-match-schema** — mapped 50 / 50 columns (0 unmatched) onto ``Sources``, | ||
| ``RadialVelocities``, ``ProperMotions``, ``Photometry``, ``Morphology``, and | ||
| ``ModeledParameters``. | ||
| #. **astrodb-generate-schema** / **astrodb-validate-schema-mapping** — produced the | ||
| Felis ``schema.yaml`` (``felis validate`` passing) and confirmed 0 nullable | ||
| violations and 0 type mismatches against the real data. | ||
| #. **astrodb-create-db** — created ``LocalGroupDB.sqlite`` and a matching test suite. | ||
| #. **astrodb-ingest-source** — ingested all 144 galaxies as sources, plus their | ||
| measurements (129 radial velocities, 65 proper motions, 142 V-band magnitudes, | ||
| 137 morphologies, 889 modeled parameters). |
Contributor
There was a problem hiding this comment.
Suggested change
| **Running the pipeline.** With the plan approved, the skills ran in sequence, each | |
| feeding the next: | |
| #. **astrodb-parse-data-table** — parsed all 50 columns (names, units, descriptions). | |
| #. **astrodb-match-schema** — mapped 50 / 50 columns (0 unmatched) onto ``Sources``, | |
| ``RadialVelocities``, ``ProperMotions``, ``Photometry``, ``Morphology``, and | |
| ``ModeledParameters``. | |
| #. **astrodb-generate-schema** / **astrodb-validate-schema-mapping** — produced the | |
| Felis ``schema.yaml`` (``felis validate`` passing) and confirmed 0 nullable | |
| violations and 0 type mismatches against the real data. | |
| #. **astrodb-create-db** — created ``LocalGroupDB.sqlite`` and a matching test suite. | |
| #. **astrodb-ingest-source** — ingested all 144 galaxies as sources, plus their | |
| measurements (129 radial velocities, 65 proper motions, 142 V-band magnitudes, | |
| 137 morphologies, 889 modeled parameters). |
Add that intermediary files for your inspection are put in the tmp/ folder.
Comment on lines
+105
to
+109
| .. note:: | ||
|
|
||
| It's also recommended that you give your agent a reference to the `AstroDB template <https://github.com/astrodbtoolkit/astrodb-template-db>`_ | ||
| repository, which contains example ``schema.yaml`` files and test suites for all the template tables. | ||
| This can help the agent understand how to structure the new database and its tests. |
Contributor
There was a problem hiding this comment.
I think we should fix this -- this should be in the SKILL and not the user's responsibility.
| repository, which contains example ``schema.yaml`` files and test suites for all the template tables. | ||
| This can help the agent understand how to structure the new database and its tests. | ||
|
|
||
| **Catalogs will have problems.** Claude is great at cleaning up data that doesn't |
Contributor
There was a problem hiding this comment.
Move this statement to the first paragraph which motivates these SKILLS.
Comment on lines
+115
to
+117
| **Review checkpoints with the advisor.** Because ``/advisor`` was enabled, a second | ||
| Opus 4.8 model reviewed the work at key points. This review isn't required but can | ||
| be very helpful for catching issues. |
Contributor
There was a problem hiding this comment.
Make a Claude advice section with specific notes about using Claude.
also add that it's useful, but will use more resources/tokens.
Comment on lines
+119
to
+122
| **Result.** A populated ``LocalGroupDB.sqlite`` with all 144 sources and their | ||
| measurements, 16 / 16 pytest tests passing, and a clean reload from the saved JSON. | ||
| A second ``/plan`` was used later in the same session to resolve the catalog's | ||
| numbered footnote references against its bibliography file. |
Contributor
There was a problem hiding this comment.
Suggested change
| **Result.** A populated ``LocalGroupDB.sqlite`` with all 144 sources and their | |
| measurements, 16 / 16 pytest tests passing, and a clean reload from the saved JSON. | |
| A second ``/plan`` was used later in the same session to resolve the catalog's | |
| numbered footnote references against its bibliography file. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created new subsection under "Creating a New Database" with instructions on how to use the Claude skills and then a workflow example from using it on The Local Group Galaxy data.