public-repo-operationalizer

Name: public-repo-operationalizer
Author: 100yenadmin

109stars4forks

How to install public-repo-operationalizer?

100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer

$npx -y skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-repo-operationalizer

Installs into the current project.

Summary

Use when preparing a repository, project kit, plugin, skillpack, or developer tool for public release or maintainer-ready public operations.

Files · 1

View on GitHub

SKILL.md

1	# Public Repo Operationalizer
2
3	Turn a useful repo into a public repo operational status surface: understandable,
4	safe to contribute to, clear about proof, and maintainable without private
5	context.
6
7	## Core Pattern
8
9	1. Audit repo truth: purpose, license, setup path, tests, CI, release state,
10	security posture, private-data boundaries, and current claims.
11	2. Define the public promise: what works, what is advisory, what is unproven,
12	and what the repo does not claim.
13	3. Add or repair default surfaces: `README.md`, `LICENSE`, `SECURITY.md`,
14	`CONTRIBUTING.md`, `AGENTS.md`, `.github/ISSUE_TEMPLATE/*`,
15	`.github/PULL_REQUEST_TEMPLATE.md`, and focused CI.
16	4. Add claim/proof docs when claims could drift: claim audit, source authority,
17	proof boundary, release status, and setup path.
18	5. Wire validation: docs safety scan, tests, link/image checks,
19	installer/package checks, and CI.
20	6. Close with evidence: issue/PR, commands, CI URL, risks, and next action.
21
22	## Public Safety Rules
23
24	- Do not publish raw transcripts, credentials, tokens, private paths, customer
25	data, local stores, browser/session data, or screenshots with secrets.
26	- Say "patterns that worked for us" for practice-based guidance.
27	- Cite official sources near factual pricing, cache, API, legal, or security
28	claims.
29	- Keep optional tools optional unless the repo truly depends on them.
30
31	## Default Template Bar
32
33	Contributor-facing templates should force safe evidence:
34
35	- issue templates: public-safe reproduction and redacted logs
36	- docs bug templates: wrong public claim or setup step
37	- pull request template: linked issue, changed files, validation, safety
38	boundary, claim impact, rollback notes, and agent-authored disclosure
39
40	## Scorecard
41
42	Score each category 0-2. Pass at 14/18 or higher.
43
44	\| Category \| 2 means \|
45	\| --- \| --- \|
46	\| Public promise \| README says who it helps, what it does, and what it does not prove \|
47	\| First-run path \| clone/install/setup/run commands work from a fresh checkout \|
48	\| Template completeness \| README, license, security, contributing, AGENTS, issue templates, and pull request template fit the repo \|
49	\| Claim safety \| allowed and forbidden claims are explicit and sourced where needed \|
50	\| Source/proof authority \| authoritative vs advisory sources and proof boundary are clear \|
51	\| Contributor safety \| redaction, no raw transcripts, no secrets, and no private paths are enforced \|
52	\| Validation automation \| CI, docs safety scan, tests, and link/image checks cover the public surface \|
53	\| Release readiness \| release tags, package channels, notes, or "not released yet" are clear \|
54	\| Maintainer handoff \| issue/PR/evidence paths let a future agent resume \|
55
56	Automatic blockers: secret, private path, raw transcript, missing license,
57	broken required setup command, missing install path, unbounded claim, official
58	endorsement claim, universal safety/savings claim, broken required local link,
59	or failing docs safety scan.
60
61	## Common Mistakes
62
63	- Treating README polish as operational readiness.
64	- Copying mature-repo machinery into a small v1 kit.
65	- Saying "ready" without setup-path and CI evidence.

People who liked this also viewed

6 picks

Type

public-repo-operationalizer

109stars4forks

View on GitHub

How to install public-repo-operationalizer?

100yenadmin/fable-token-saving-skills-orchestrator/public-repo-operationalizer

$npx -y skills add 100yenadmin/fable-token-saving-skills-orchestrator --skill public-repo-operationalizer

Installs into the current project.

Summary

Use when preparing a repository, project kit, plugin, skillpack, or developer tool for public release or maintainer-ready public operations.

Files · 1

View on GitHub

SKILL.md

1	# Public Repo Operationalizer
2
3	Turn a useful repo into a public repo operational status surface: understandable,
4	safe to contribute to, clear about proof, and maintainable without private
5	context.
6
7	## Core Pattern
8
9	1. Audit repo truth: purpose, license, setup path, tests, CI, release state,
10	security posture, private-data boundaries, and current claims.
11	2. Define the public promise: what works, what is advisory, what is unproven,
12	and what the repo does not claim.
13	3. Add or repair default surfaces: `README.md`, `LICENSE`, `SECURITY.md`,
14	`CONTRIBUTING.md`, `AGENTS.md`, `.github/ISSUE_TEMPLATE/*`,
15	`.github/PULL_REQUEST_TEMPLATE.md`, and focused CI.
16	4. Add claim/proof docs when claims could drift: claim audit, source authority,
17	proof boundary, release status, and setup path.
18	5. Wire validation: docs safety scan, tests, link/image checks,
19	installer/package checks, and CI.
20	6. Close with evidence: issue/PR, commands, CI URL, risks, and next action.
21
22	## Public Safety Rules
23
24	- Do not publish raw transcripts, credentials, tokens, private paths, customer
25	data, local stores, browser/session data, or screenshots with secrets.
26	- Say "patterns that worked for us" for practice-based guidance.
27	- Cite official sources near factual pricing, cache, API, legal, or security
28	claims.
29	- Keep optional tools optional unless the repo truly depends on them.
30
31	## Default Template Bar
32
33	Contributor-facing templates should force safe evidence:
34
35	- issue templates: public-safe reproduction and redacted logs
36	- docs bug templates: wrong public claim or setup step
37	- pull request template: linked issue, changed files, validation, safety
38	boundary, claim impact, rollback notes, and agent-authored disclosure
39
40	## Scorecard
41
42	Score each category 0-2. Pass at 14/18 or higher.
43
44	\| Category \| 2 means \|
45	\| --- \| --- \|
46	\| Public promise \| README says who it helps, what it does, and what it does not prove \|
47	\| First-run path \| clone/install/setup/run commands work from a fresh checkout \|
48	\| Template completeness \| README, license, security, contributing, AGENTS, issue templates, and pull request template fit the repo \|
49	\| Claim safety \| allowed and forbidden claims are explicit and sourced where needed \|
50	\| Source/proof authority \| authoritative vs advisory sources and proof boundary are clear \|
51	\| Contributor safety \| redaction, no raw transcripts, no secrets, and no private paths are enforced \|
52	\| Validation automation \| CI, docs safety scan, tests, and link/image checks cover the public surface \|
53	\| Release readiness \| release tags, package channels, notes, or "not released yet" are clear \|
54	\| Maintainer handoff \| issue/PR/evidence paths let a future agent resume \|
55
56	Automatic blockers: secret, private path, raw transcript, missing license,
57	broken required setup command, missing install path, unbounded claim, official
58	endorsement claim, universal safety/savings claim, broken required local link,
59	or failing docs safety scan.
60
61	## Common Mistakes
62
63	- Treating README polish as operational readiness.
64	- Copying mature-repo machinery into a small v1 kit.
65	- Saying "ready" without setup-path and CI evidence.

People who liked this also viewed

6 picks

Type