docs: add a skill for adding a new /team profile - #48
Merged
Conversation
Documents the procedure for adding an advisor, staff member, cohort researcher, or collaborator to the Team page: the required TeamMember fields, the headshot intake and optimize:images step, the slug-uniqueness and cohort-count invariants check:content enforces, and the validation/visual-check sequence. Includes a worked example using Brianna Gabaldon (Microsoft Product Manager, NYU CGA grad, advisor) with the still-unverified fields - photo, LinkedIn, specific advisory focus, and bio - left as explicit placeholders rather than fabricated, per the content guide's rule against publishing unverified biographical claims. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adding the add-team-profile skill broke CI: Tailwind v4 scans every non-ignored file for candidate utility names, not just component classNames, and the skill's prose used a plain English word that is also a valid single-word Tailwind utility, so the build compiled in an unused rule the committed static-site/ snapshot didn't have. Tried excluding .github/ from the scan via @source not in globals.css first. That produced a byte-for-byte identical build on Windows (verified by SHA-256 against the committed snapshot), but the same commit failed CI on Linux - a downloaded build artifact from the failing run showed the directive had no effect there. Reverted rather than ship a fix confirmed to only work on one platform; recorded as UPD-018 in UPDATES-NEEDED.md for a follow-up with Linux access. Shipped fix: reword the two sentences in the skill that used the word verbatim, and one unrelated instance of another single-word utility name found during a fuller scan. Verified with a clean-cache rebuild: the resulting CSS is byte-for-byte identical (SHA-256 match) to what is already committed, so no snapshot regeneration is needed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
yorkerhodes3
force-pushed
the
agents/refresh-from-github-repo
branch
2 times, most recently
from
August 27, 2026 15:18
a58e008 to
3b803e2
Compare
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
1 participant
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.
What
A repository skill at
.github/skills/add-team-profile/SKILL.mddocumenting the procedure for adding or updating anyone on/team- an advisor, staff member, cohort researcher, or collaborator.Requested directly, with Brianna Gabaldon (Microsoft Product Manager, NYU CGA grad, joining as an advisor) as the worked example.
Why this shape
.github/skills/{name}/SKILL.mdwithname/descriptionfrontmatter.docs/CONTENT-GUIDE.md(field reference) andCONTRIBUTING.md(branch/validate/publish workflow).check:contentenforces: slugs are unique across every category (not per-list), and the three-place cohort-count reconciliation only applies toresearchers.A CI failure worth knowing about
The first version of this skill broke the build in a way worth recording: Tailwind v4 scans every non-ignored file for candidate utility names, not just component classNames, and the skill's prose used a plain English word that also happens to be a valid single-word Tailwind utility - so an unused CSS rule for it got compiled in, and the committed
static-site/snapshot no longer matched a fresh build.Tried excluding
.github/from Tailwind's scan via@source notinglobals.cssfirst - verified byte-for-byte identical to the committed snapshot on Windows, but the identical commit failed on the Linux CI runner, where a downloaded build artifact showed the exclusion had no effect. Reverted that config change rather than ship something confirmed to only work on one platform, and recorded it as UPD-018 inUPDATES-NEEDED.mdfor a follow-up with Linux access.The shipped fix is simpler and platform-independent: reword the sentences that used the word verbatim (plus one similar case found during a fuller scan), so it never appears in scanned prose at all. Verified with a clean-cache rebuild that the resulting CSS is byte-for-byte identical to what's already committed - and now confirmed by this PR's own green CI run on Linux.
Verified
static-site/snapshot - no snapshot regeneration needed.