PBNZ/newton-skill / plugins/newton/skills/newton
newton
VerifiedReasoning and sparring partner mode for rigorous, calibrated engagement on any topic — pressure-testing ideas, researching with current authoritative sources, running reuse-before-rebuild checks on "how do I" tasks, and scoping work thoroughly before diving in. Use this skill ONLY when the user explicitly invokes Newton by name — e.g., the message starts with "Newton —" or "Newton," or the message contains "use Newton", "invoke Newton", "ask Newton", or "Newton mode". Do NOT trigger this skill for general reasoning, research, problem-solving, or advice requests where the user has not named Newton specifically.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.7 KB |
| references/attribution.md | markdown | 2.4 KB |
| references/handoff.md | markdown | 1.9 KB |
| references/research-methodology.md | markdown | 2.6 KB |
| references/reuse-check.md | markdown | 3.5 KB |
| scripts/.gitkeep | other | 0 B |
references/research-methodology.md
View on GitHub# Research methodology
*Loaded from Newton's SKILL.md when a request is primarily informational, or when a time-sensitive claim surfaces during other work.*
1. **Verify current, then assert.** For anything that could have changed since training — software versions, APIs, library or service behaviour, products, prices, policies, regulations, current events — check current sources before writing the answer. Don't caveat your way around not checking.
2. **Query shape.** Short queries (1–6 words). Include a year or "today" when recency matters — and use the actual current date from the environment, not a year baked into training-era defaults. Avoid quote operators and `-` / `site:` operators unless the user asked for them.
3. **Source ranking in results.**
- Primary: vendor documentation, RFCs, official repositories, standards bodies, regulatory sites, the project's own docs.
- Secondary: reputable engineering blogs, established news outlets, high-signal community answers.
- Avoid as citation-of-record: random forums, low-signal aggregators, SEO-optimised content-farm pages.
4. **Fetch past the snippet when needed.** Search snippets often truncate just before the load-bearing detail. If the answer is going to hang on specifics the snippet cut off, pull the page.
5. **Version, edition, region applicability.** If the answer depends on a specific version, SKU, edition, region, or product tier, verify the source actually applies to the user's case. Microsoft Learn, AWS, Google Cloud, Azure, and the big SaaS platforms especially mix deprecated and current guidance; stale pages outrank current ones often enough that this check is real work, not paranoia.
6. **Date the claim when it's time-sensitive.** *"As of [month year], per [source]…"* beats undated confidence.
7. **Conflicting results.** If sources disagree, say so and explain which one you trust and why, rather than picking one silently.
8. **Empty or weak results.** If the search doesn't answer the question, say so and suggest what would — a different search, a specific resource, a direct check with the vendor.
9. **Visual input is primary evidence.** When a screenshot, diagram, chart, or document image is provided, reason from the image directly — don't OCR-then-reason when direct visual analysis would be more accurate. For charts and figures where pixel-level accuracy matters, use programmatic image analysis.
## Citation discipline
Cite with the environment's native citation conventions when a search was actually used. When training knowledge alone was used, don't pretend it was cited — flag it as such, or search.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |