Skip to content

Add notion-spec-to-implementation and quantitative-resume-auditor skills - #1245

Open
mrdesouzaphd-cmyk wants to merge 42 commits into
anthropics:mainfrom
mrdesouzaphd-cmyk:main
Open

mrdesouzaphd-cmyk wants to merge 42 commits into
anthropics:mainfrom
mrdesouzaphd-cmyk:main

Conversation

@mrdesouzaphd-cmyk

Copy link
Copy Markdown

Notion Spec to Implementation Skill

This skill transforms product or tech specs into concrete Notion tasks that Claude code can implement. It breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking.

What it does

  • Fetches spec documents from Notion using the Notion MCP integration
    • Extracts and structures requirements from the spec
    • Creates implementation plans with phases and milestones
    • Creates individual tasks with acceptance criteria and dependencies
    • Maintains bidirectional links between specs, plans, and tasks
    • Tracks progress and handles spec changes

Note: Requires Notion MCP Integration

This skill uses the Notion MCP integration (Notion:notion-search, Notion:notion-fetch, Notion:notion-create-pages). A connected Notion workspace is required for full functionality.

This skill transforms product or tech specs into actionable Notion tasks and implementation plans, including task structures and progress tracking.
Added detailed documentation for the quantitative resume auditor skill, including instructions, core formula, and usage examples.New skill that audits resumes by computing metric density (M/B ratio) using Python. Benchmarks against a 3.0 Gold Standard. Includes JD gap analysis. Apache 2.0 licensed. Author: Dr. Adriano De Souza.
Updated author name and enhanced skill description for clarity.
This file provides benchmarks, metric categories, and a JD coverage framework for the Quantitative Resume Auditor. It includes guidelines for evaluating resumes based on quantifiable achievements and mapping them to job descriptions.
@mrdesouzaphd-cmyk mrdesouzaphd-cmyk changed the title Add notion-spec-to-implementation skill Add notion-spec-to-implementation and quantitative-resume-auditor skills Jun 5, 2026
@mrdesouzaphd-cmyk

Copy link
Copy Markdown
Author

Quantitative Resume Auditor — skill added in this PR

Author: Dr. Fabiano de Souza
Files: skills/quantitative-resume-auditor/SKILL.md, REFERENCE.md
License: Apache 2.0

What it does

Turns a resume review from a subjective opinion into a calculated score. The skill counts every numeric data point in a resume, runs Python to compute a Metric Density ratio (M/B), and shows the user exactly which bullets are pulling the score down.

Formula: Density = Total Numeric Metrics (M) / Total Bullet Points (B)

A score of 3.0 or above is the target (Gold Standard).

How it works

  1. Claude reads the resume and counts bullet points (B), numeric metrics (M), and quantified bullets (Q) across seven categories: percentages, currency, headcount, years/time, score gains, efficiency, and volume.
  2. Python code executes the audit and returns the density score, quantification rate, status, and a recommendation.
  3. Claude delivers three sections: Audit Scoreboard, Category Breakdown, and Gap Analysis (with or without a job description).

Trigger phrases

  • "Audit this resume for data density."
  • "Score my resume against the 3.0 benchmark."
  • "Run a gap analysis — here is my resume and the job description."
  • "Is my resume quantitative enough?"

Notes

  • Requires code execution enabled in Claude.
  • The 3.0 benchmark is a professional heuristic developed from analysis of executive resumes, not a published HR standard.
  • Works across all professions: education, business, healthcare, technology, government, nonprofit.

@98zc5g5jyw-arch

Copy link
Copy Markdown

Thanks for the clean-up push — the placeholder files are gone, and this now adds exactly two skills. Reviewed the new head (1cc4759) against the repo conventions: notion-spec-to-implementation is in good shape, but quantitative-resume-auditor has two issues that need fixing before it can land.

quantitative-resume-auditor

  1. Fails skill validation. The file starts with an HTML comment (<!-- SPDX-License-Identifier: Apache-2.0 ... -->) before the --- block, so skill-creator/scripts/quick_validate.py reports "No YAML frontmatter found". The frontmatter must be the first thing in SKILL.md — move the SPDX note below it (or into LICENSE.txt).
  2. The document is two drafts concatenated. The first copy is cut off mid-sentence ("...Flag any that are missing as HIGH RISK — these are the", line 168), and the whole skill restarts at line 178 (# Quantitative Resume Auditor again), preceded by an orphaned SPDX comment fragment and a second name:/description: frontmatter block (lines 169-176). Suggest keeping the complete second version (with the B/C subsections and the examples) and deleting the truncated first copy plus the duplicated frontmatter.
  3. Also on the license: thanks for adding LICENSE.txt — but it's an abridged Apache-2.0 (161 lines, no APPENDIX, different definition text) vs. the canonical ~201-line text every other skill here ships; worth using the full text.
  4. No .claude-plugin/marketplace.json entry for either skill — without one they aren't installable from the marketplace (cf. Add md2video-audio skill #1703 / Add resume-screening skill #1763 / Add pyxel skill for retro game development #525).

notion-spec-to-implementation

  • ✅ Frontmatter valid, quick_validate.py → "Skill is valid!"; all eight referenced examples/ + reference/ files exist; both evaluations/*.json parse; Apache-2.0 LICENSE.txt included.
  • ✅ Clear, actionable workflow; markdown-only (no scripts), and a scan for dangerous patterns came back clean.
  • Nit: the workflow depends on the Notion:* MCP tools (notion-search / notion-fetch / notion-create-pages / notion-update-page), but the prerequisite isn't stated anywhere — declaring it (e.g. a compatibility: line) would help users know the Notion MCP server is required.
  • Nit: 15 of the 19 skills here carry a license: frontmatter field (this one has name/description only).

Happy to re-review once the quantitative-resume-auditor file is deduped and clean.

@98zc5g5jyw-arch

Copy link
Copy Markdown

Reviewed at head 5c4fbfc. The push since our last review (1cc4759) is 7 files / +370 — it packages brianjosh as an OpenAI/Codex plugin and leaves every file from the earlier review byte-identical, so the four asks from 2026-09-16 are still open. Whole PR at this head: 26 files, +3,784 vs merge-base.

Prior asks — status at 5c4fbfc

  1. ❌ quantitative-resume-auditor still fails skill validation. quick_validate.py skills/quantitative-resume-auditor → No YAML frontmatter found — SKILL.md still opens with the SPDX HTML comment (lines 1–5) before the --- block. Blob cac2233 is unchanged from 1cc4759.
  2. ❌ Still two drafts concatenated: the first copy is cut off mid-sentence at line 168 ("...Flag any that are missing as HIGH RISK — these are the"), followed by an orphaned SPDX fragment (169–171), a second name:/description: frontmatter (173–176) and # Quantitative Resume Auditor again at line 178.
  3. ❌ skills/quantitative-resume-auditor/LICENSE.txt is still the abridged Apache-2.0: 161 lines, no APPENDIX, vs the 201-line text in skills/notion-spec-to-implementation/LICENSE.txt, skills/skill-creator/LICENSE.txt and skills/mcp-builder/LICENSE.txt.
  4. ❌ Neither skill is in .claude-plugin/marketplace.json (file unchanged, 03d8e71; grep for both skill names finds nothing) — they still aren't installable from the repo's Claude marketplace.

New in this push — verified

  • ✅ plugins/brianjosh/skills/brianjosh/SKILL.md frontmatter is valid: quick_validate.py plugins/brianjosh/skills/brianjosh → Skill is valid!.
  • ✅ plugins/brianjosh/plugin.json validates against the $schema it declares — ran jsonschema 4.26.0 against the fetched agent-plugins.org/schemas/1.0.0/plugin.schema.json: valid (required $schema + name present, no keys outside additionalProperties: false).
  • ✅ .agents/plugins/marketplace.json matches the layout OpenAI documents for a repo-scoped marketplace ($REPO_ROOT/.agents/plugins/marketplace.json; entry shape source{source:"local",path:"./plugins/brianjosh"}, policy.installation, policy.authentication, category) — checked against developers.openai.com/plugins/build/plugins.
  • ✅ Static scan for urlopen|requests|subprocess|os.system across plugins/, .agents/ and brianjosh/ → no code hits (only two prose matches for the word "requests" in SKILL.md). The plugin ships no scripts, and assets/icon.svg is a plain 8-line inline SVG — no <script>, foreignObject or external references.

Blocking

  • Item 1 above: while SKILL.md's first content is not the --- frontmatter block, the skill cannot validate or load, so quantitative-resume-auditor still can't land (item 2 is in the same file and worth fixing in the same edit).

Non-blocking notes

  • plugins/brianjosh/ ships no LICENSE (18 of the 19 skills/* folders here carry a LICENSE.txt; only skills/doc-coauthoring doesn't) and plugin.json omits the optional license field — adding both would match repo convention.
  • brianjosh/references/interview-source.md (new 202-line file in a new top-level brianjosh/ folder) is referenced by nothing in the tree; the plugin README and SKILL.md both load skills/brianjosh/references/dr-de-souz-ai-source-notes.md instead. Looks like a stray copy — consider moving it under the plugin folder or dropping it.
  • .agents/ and plugins/ are two new root-level folders not in the README's layout list (./skills, ./spec, ./template), and the repo-scoped marketplace is named dr-desouz-ai-skills (displayName "Dr. De.Souz.AI Skills") while living in anthropics/skills — a repo-scoped marketplace takes the host repo as its identity, so that naming may read oddly if this is merged upstream rather than consumed from the fork.
  • notion-spec-to-implementation is unchanged and keeps its two earlier nits: the Notion MCP prerequisite (Notion:notion-search / notion-fetch / notion-create-pages / notion-update-page) still isn't declared, and frontmatter has no license: field (15 of 19 skills here set one).

Happy to re-review once the quantitative-resume-auditor frontmatter and duplicate block are cleaned up.

@98zc5g5jyw-arch

Copy link
Copy Markdown

Reviewed at head 72064a2 — incremental check of the new push: one commit, "Add new skills to marketplace.json", +19/−2, touching only .claude-plugin/marketplace.json.

Resolved since the 2026-09-24 review

  • ✅ Ask 4 (marketplace): both skills are now listed — notion-spec-to-implementation and quantitative-resume-auditor (entries at marketplace.json:53–70; source: "./", strict: false, skill paths resolve to real directories). The file parses (python3 -m json.tool) and both entries match the shape of the existing plugins. The stray }/, split at the old line 43 is normalised too.

Still open at this head (verified, unchanged from 5c4fbfc)

  1. ❌ quantitative-resume-auditor/SKILL.md still fails quick_validate.py → No YAML frontmatter found: the file opens with the SPDX HTML comment (lines 1–5), and the validator requires the content to start with ---. Moving that comment below the frontmatter — or dropping it and adding license: Apache-2.0 to the frontmatter, which the validator accepts and many skills here set — clears it; the duplicate block in item 2 can be cleaned in the same edit.
  2. ❌ The concatenated second draft is still present (~lines 158–186): cut-off sentence, orphaned SPDX fragment, second name:/description: block, second # Quantitative Resume Auditor.
  3. ❌ skills/quantitative-resume-auditor/LICENSE.txt is still the abridged 161-line Apache-2.0 (no APPENDIX), vs the 201-line text in skills/notion-spec-to-implementation/LICENSE.txt and skills/skill-creator/LICENSE.txt.
  4. ℹ️ GitHub still reports this branch as CONFLICTING against main — a rebase will be needed before it can merge.

notion-spec-to-implementation still validates (Skill is valid!).

Happy to re-review once SKILL.md's frontmatter and duplicate block are cleaned up — both live in the same file.

@98zc5g5jyw-arch

Copy link
Copy Markdown

Reviewed at head a24bc6e — incremental check of the new merge (parents 72064a2 + upstream 3337550).

  • Conflict resolved: gh pr view 1245 now reports mergeable: MERGEABLE (previously CONFLICTING). mergeStateStatus is BLOCKED, which reflects review gating, not a conflict — the branch itself merges cleanly.
  • The merge only pulled in upstream commits plus a .claude-plugin/marketplace.json update (parses cleanly, both new skills listed exactly once, no duplicates). Diffing the two new skill directories against our previous review ref (72064a2) is empty, so both open items stand:
    1. skills/quantitative-resume-auditor/SKILL.md still fails validation — the SPDX comment precedes the opening ---, so quick_validate.py returns No YAML frontmatter found (exit 1). The concatenated duplicate draft (~lines 158–186) is likewise unchanged.
    2. skills/quantitative-resume-auditor/LICENSE.txt is still the abridged 161-line Apache-2.0; the canonical 201-line text (as in skills/notion-spec-to-implementation/LICENSE.txt) is expected.

No re-review needed once those two are fixed — happy to re-check after the next push.

Moved the SPDX license comment below the YAML frontmatter to resolve the validation script error.

Removed the concatenated duplicate draft of the skill from the bottom of the file as requested in PR anthropics#1245 feedback.
Added the Apache License 2.0 to the project for legal compliance and usage terms.
@mrdesouzaphd-cmyk

Copy link
Copy Markdown
Author

@Ronin1351, I sincerely apologize for the unwanted notifications. Unfortunately, I’m unable to remove you from the notification list manually. You can unsubscribe by following either of these options:

Open one of the GitHub notification emails you received.
Scroll to the bottom of the email.
Click the Unsubscribe link.

Alternatively, on this pull request page:

Locate the notification settings in the right sidebar.
Click the Unsubscribe button.

Thank you for your understanding, and I apologize again for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants