GitHub Issues
github/awesome-copilot
Create, update, and manage GitHub issues using MCP tools. An agent skill from github/awesome-copilot.
Agent skill
Software Engineering Standards Reference
A skill your agent uses when you need to reference, cite, or apply software engineering standards.
Install Software Engineering Standards Reference
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-reference --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .claude/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .claude/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-referenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-reference --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .agents/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .agents/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-reference --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .cursor/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .cursor/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kitchen-engineer42/pdf2skills.git --path 'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference'--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-reference --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .gemini/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .gemini/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-referenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .github/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .github/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kitchen-engineer42/pdf2skills software-engineering-standards-reference --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kitchen-engineer42/pdf2skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/'skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference' .opencode/skills/software-engineering-standards-reference && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "software-engineering-standards-reference" agent skill from https://github.com/kitchen-engineer42/pdf2skills/tree/main/skills_samples/Steve%20McConnell%20Code%20Complete%20A%20Practical%20Handbook%20of%20Software%20Construction_output/software-engineering-standards-reference into .opencode/skills/software-engineering-standards-reference/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "software-engineering-standards-reference", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
software-engineering-standards-reference- GitHub stars
- 134
- Token cost
- ~681 tokens
- SKILL.md length
- 276 words
- Files
- 2 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when you need to reference, cite, or apply software engineering standards.
- Works in 4 steps: Identify your domain: Determine whether… → Find the specific standard: Use the… → Apply the naming convention: Reference… → …
- You need to reference
- SKILL.md covers When to Use, Standard Naming Convention, Top-Level Lifecycle Standard and Finding the Right Standard, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Software Engineering Standards Reference is an agent skill from kitchen-engineer42/pdf2skills. Use this skill when you need to reference, cite, or apply software engineering standards. This skill provides the IEEE/ISO standard naming convention and categorized lists of standards for software development, quality assurance, and project management.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/standards-lists.md`).
It sits in Testing & QA, covering QA and bug reports, Project management and Audit readiness. The repository describes itself as: Convert a book into skills directly callable to Claude Code.
When your agent uses it
- You need to reference
- Apply software engineering standards
Example prompts
- “/software-engineering-standards-reference”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify your domain: Determine whether you need development, QA, or management standards
- Find the specific standard: Use the categorized lists to locate the standard matching your activity
- Apply the naming convention: Reference standards using the proper format
- Check for updates: Verify you are using the current version of the standard
What it can do on your machine
Read from SKILL.md and the folder at commit 0d70065. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Software Engineering Standards Reference loads about 681 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 276 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 276 words (~681 tokens).
“Software engineering standards provide established best practices for development, quality assurance, and project management. Use this skill to properly reference standards and find the appropriate standard for your needs.”
- name
- software-engineering-standards-reference
Files
SKILL.md and 1 other file (references) in skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference of kitchen-engineer42/pdf2skills.
- SKILL.md
- references/standards-lists.md
Open the folder on GitHubat commit 0d70065
Compare with similar skills
Software Engineering Standards Reference next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Software Engineering Standards Reference this skillkitchen-engineer42/pdf2skills | 134 | — | ~681 | Automated safety check: Pass | None | |
| GitHub Issuesgithub/awesome-copilot | 40k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Qe Quality Assessmentproffesor-for-testing/agentic-qe | 494 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Fix The Classjoetawil7/first-pass | 112 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Dogfood Exploratory QAvercel-labs/agent-browser | 44k | 8 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| DeerFlow Smoke Testbytedance/deer-flow | 83k | — | ~2.5k | Automated safety check: Notes | MIT |
Similar skills
- Official
Qe Quality Assessment
proffesor-for-testing/agentic-qe
Comprehensive quality gates, metrics analysis, and deployment readiness assessment for continuous quality assurance.
Fix The Class
joetawil7/first-pass
Bug-fix routine that fixes the whole class of bug, not just the reported instance.
- Official
Dogfood Exploratory QA
vercel-labs/agent-browser
Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.
DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
CodexBar Live QA
steipete/CodexBar
Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.
More from kitchen-engineer42/pdf2skills
All 21 skills in this repoCode Commenting Strategy
kitchen-engineer42/pdf2skills
Apply strategic approaches to code commenting including when to comment, optimal comment density, performance considerations, and integration with development workflow.
Software Engineering Standards
kitchen-engineer42/pdf2skills
Reference and apply IEEE, ISO/IEC, and other software engineering standards for development, quality assurance, and project management.
Complex Conditional Refactoring
kitchen-engineer42/pdf2skills
Refactor complex case statements and deeply nested code using appropriate strategies.
Pseudocode Programming Process
kitchen-engineer42/pdf2skills
A skill your agent uses when implementing complex logic, developing functions, or designing algorithms.
Class Organization And Layout
kitchen-engineer42/pdf2skills
Organize class members in standard order, separate classes with blank lines, and maintain one-class-per-file structure.
Code Commenting Checklists
kitchen-engineer42/pdf2skills
Use specific checklists to ensure comprehensive and high-quality code commenting for general code, data declarations, and program structures.
Related
Categories
Questions about Software Engineering Standards Reference
What does Software Engineering Standards Reference do?
A skill your agent uses when you need to reference, cite, or apply software engineering standards. Software Engineering Standards Reference is an agent skill from kitchen-engineer42/pdf2skills. Use this skill when you need to reference, cite, or apply software engineering standards.
When should I use Software Engineering Standards Reference?
Software Engineering Standards Reference fits situations like: you need to reference; apply software engineering standards.
How do I install Software Engineering Standards Reference in Claude Code?
Run `npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a claude-code`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference in kitchen-engineer42/pdf2skills) into .claude/skills/software-engineering-standards-reference in your project. Claude Code loads it when a task matches its description.
How do I install Software Engineering Standards Reference in Codex?
Run `npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a codex`. Or copy the skill folder (skills_samples/Steve McConnell Code Complete A Practical Handbook of Software Construction_output/software-engineering-standards-reference in kitchen-engineer42/pdf2skills) into .agents/skills/software-engineering-standards-reference in your project. Codex loads it when a task matches its description.
Can I use Software Engineering Standards Reference in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kitchen-engineer42/pdf2skills --skill software-engineering-standards-reference -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/software-engineering-standards-reference, .gemini/skills/software-engineering-standards-reference, .github/skills/software-engineering-standards-reference and .opencode/skills/software-engineering-standards-reference in your project.
What does Software Engineering Standards Reference need to run?
SKILL.md names no scripts, command-line tools or credentials: Software Engineering Standards Reference is instructions for the agent only.
Does Software Engineering Standards Reference access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Software Engineering Standards Reference safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Software Engineering Standards Reference use?
No licence was found for Software Engineering Standards Reference or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Software Engineering Standards Reference use?
About 681 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 584 tokens, read only when the agent opens those files.
What are the alternatives to Software Engineering Standards Reference?
Skills that share tags, products or a category with Software Engineering Standards Reference: GitHub Issues (github/awesome-copilot, 40k stars), Qe Quality Assessment (proffesor-for-testing/agentic-qe, 494 stars), Fix The Class (joetawil7/first-pass, 112 stars) and Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Software Engineering Standards Reference?
kitchen-engineer42 (a GitHub user) maintains it in kitchen-engineer42/pdf2skills, which has 134 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on February 24, 2026.
Source: kitchen-engineer42/pdf2skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.