
glycoengineering
Analyzes and engineers protein glycosylation by scanning canonical N-glycosylation sequons, describing S/T-rich regions, checking curated glycan evidence, and preparing NetNGlyc, NetOGlyc and GlycoSHIELD workflows. Use for glycoprotein engineering, antibody Fc glycosylation, glycan shielding, and site-specific glycoproteomics interpretation.
- Installs
- 1.9K
- Last 24h
- +13
- Trending rank
- #7559
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill glycoengineering- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads glycoengineering automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Glycoengineering
When to use
Use for canonical N-glycosylation candidate analysis, O-GalNAc candidate triage, antibody glycoform comparison, or structural glycan shielding. Keep four kinds of result separate: sequence motif, prediction, experimentally supported occupancy, and glycan structure/composition. None alone establishes all the others.
This workflow focuses on eukaryotic secretory-pathway N-glycosylation and mucin-type O-GalNAc. O-GlcNAc, O-mannose, O-fucose and other O-linked modifications require appropriate evidence and predictors; S/T enrichment does not identify the type.
Workflow
- Record the protein accession, isoform/version, exact sequence, expression host, signal peptide/transmembrane topology and construct boundaries. Preserve a mapping from submitted sequence coordinates to mature protein, PDB chain/residue identifiers and antibody numbering where relevant.
- Scan canonical N-X-[S/T] candidates with X not Pro. Retain overlaps:
NNSThas candidates starting at 1 and 2. A missing canonical motif does not rule out unusual N-glycosylation; a present motif does not establish occupancy. - Prioritize secreted/luminal/extracellular regions using topology and curated evidence. Sequence-only results in a cytoplasmic region are not evidence of secretory-pathway glycosylation.
- For O-GalNAc, use S/T density only as a descriptive feature, then inspect a suitable predictor and cell/transferase context. Do not exclude SP/TP motifs: adjacent Pro can be favorable, depending on the GalNAc-transferase and context. See the GalNAc-T substrate study.
- Propose explicitly numbered mutations, list every changed residue and rescan the full product for lost/created overlapping motifs. Evaluate structural and expression effects independently of glycosylation.
- Validate occupancy and glycoforms experimentally, with localization evidence, glycan composition/structure confidence, and the biological assay required by the engineering objective. For biosimilar comparisons, match sample handling, analytical coverage and quantification before comparing glycan percentages.
Local sequence analysis
The standard-library helper scripts/glycoengineering_tools.py
replaces copied snippets. Import it with this skill's scripts/ directory on
PYTHONPATH, or run Python from that directory. It accepts raw canonical
20-amino-acid sequences, normalizes whitespace/case, and rejects FASTA headers,
gaps, unknown residues and empty input. Parse FASTA records first; do not remove
unknown residues because that changes coordinates. Coordinates are 1-based in the
normalized submitted sequence.
from glycoengineering_tools import (
normalize_sequence, find_n_glycosylation_sequons,
eliminate_glycosite, add_glycosite, find_st_rich_sites,
)
sequence = normalize_sequence("NNST")
sites = find_n_glycosylation_sequons(sequence)
assert [site["position"] for site in sites] == [1, 2]
mutant = eliminate_glycosite(sequence, 1, "Q")
assert mutant == "QNST" # the overlapping sequon at position 2 remains
assert [site["position"] for site in find_n_glycosylation_sequons(mutant)] == [2]
# Three intended changes: A1N, P2A, A3T. P->A must be explicit.
parent = "APA"
product = add_glycosite(parent, 1, "T", allow_proline_substitution=True)
changes = [(i, before, after) for i, (before, after) in
enumerate(zip(parent, product), 1) if before != after]
assert product == "NAT" and len(changes) == 3
# Density is a fraction of residues, not an O-glycosylation probability.
o_candidates = find_st_rich_sites("STPST", window=7, min_st_fraction=0.4)
assert [site["position"] for site in o_candidates] == [1, 2, 4, 5]
eliminate_glycosite requires a complete canonical sequon and a one-residue
replacement other than N. add_glycosite can alter up to three residues; it retains
an existing S/T at +2. Neither function predicts a mutant's fold, glycan occupancy,
function or tolerability. An N-to-Q substitution can change protein behavior even
without a glycan effect.
The S/T density window must be a positive odd integer. Terminal windows shorten, and their denominator is the actual window length. Dense regions may help triage mucin-like sequence; isolated real O-GalNAc sites can be missed.
For batch analysis, keep identifiers and normalized sequence lengths:
sequences = {"overlap": "NNST", "control": "APAA", "mucin_like": "STPST"}
rows = []
for name, raw_sequence in sequences.items():
seq = normalize_sequence(raw_sequence)
positions = [site["position"] for site in find_n_glycosylation_sequons(seq)]
rows.append({"protein": name, "length": len(seq),
"n_sequon_positions": positions,
"n_sequons_per_100_residues": 100 * len(positions) / len(seq),
"st_rich_positions": [site["position"] for site in find_st_rich_sites(seq)]})
Prediction services
Use the official forms, which accept FASTA and return web results; this skill does not provide a stable submission API or job-polling endpoint. Saving a CGI URL is not a submitted job. Preserve the output, input and service version together.
| Service | Current documented scope and interpretation |
|---|---|
| NetNGlyc 1.0 | Human N-glycosylation; reports network potential and jury agreement. Default threshold 0.5; not a calibrated occupancy probability. Up to 2,000 sequences / 200,000 residues total / 4,000 per sequence. SignalP runs, but extracellular topology is not checked. The server may score N-P-S/T; exclude these from the canonical candidate set unless independent evidence warrants review. |
| NetOGlyc 4.0 | Mammalian mucin-type O-GalNAc; outputs GFF2 confidence scores, with scores greater than 0.5 marked positive. Up to 50 sequences / 200,000 residues total / 4,000 per sequence. Prefer full sequence including signal peptide; isolated sites need 15 residues of flanking context on both sides. A positive supports regional likelihood, not guaranteed site occupancy or glycan type beyond this model's O-GalNAc scope. |
The service documentation and sample output were reviewed; new prediction jobs were not submitted during this refresh.
Structural shielding with GlycoSHIELD
GlycoSHIELD grafts pre-simulated glycan conformers onto protein structures and filters steric clashes. It does not predict which sequons are occupied or run fresh molecular dynamics for each query. See Tsai et al., 2024.
Read references/glycoshield.md for the pinned source,
installation, direct Python API, input mapping and SASA analysis. The reviewed
upstream CLI silently ignores several parsed options, including --mode,
--threshold and --dryrun; use the documented direct API workaround. Outputs
include per-site PDB/XTC ensembles and shielding encoded in a PDB B-factor column;
those values are not crystallographic temperature factors.
Database evidence and glycan notation
Read references/glycan_databases.md for the live GlyTouCan SPARQL lookup, GlyConnect access limitations, curated resources and notation. Query exact accessions and preserve dataset/source dates, species, tissue/cell context and supporting publications. Missing records or service errors cannot establish that a protein is unglycosylated.
A monosaccharide composition such as Hex:5 HexNAc:4 dHex:1 does not resolve
linkages, branch positions, or distinguish GlcNAc from GalNAc. A cartoon without
linkages is schematic, not IUPAC condensed notation. Use an actual sequence
(WURCS/GlycoCT/IUPAC with its uncertainty retained) and accession when available.
Core fucose attaches to the innermost GlcNAc of an N-glycan, not to core mannose.
Antibody engineering decisions
Number Fc mutations in an explicit scheme (commonly EU), then map them to the actual construct. EU N297 is not residue 297 of an isolated Fc FASTA. Fc glycans and any Fab glycans must be distinguished analytically.
| Objective | Candidate strategy | Required interpretation |
|---|---|---|
| Increase FcγRIIIa engagement / ADCC | Reduce Fc core fucosylation while preserving the glycan | Effect size depends on antibody, receptor and assay; do not assume a universal fold gain. Structural evidence. |
| Remove canonical Fc N-glycosylation | N297Q/A/D or disrupt the +2 residue with T299A | Sequon disruption; not a guarantee of otherwise unchanged structure or effector function. Verify the actual product. |
| Alter serum persistence | Characterize glycoform-specific clearance with the relevant protein | IgG high-mannose clearance can increase; sialylation is not a universal IgG half-life recipe. Human PK study. |
| Investigate anti-inflammatory Fc activity | Compare defined sialylated glycoforms | Linkage, preparation and biological model matter. Positive results in particular models do not establish a universal IVIG mechanism. Defined Fc study. |
| Reduce non-human glycan epitopes | Measure α-Gal and Neu5Gc and select compatible production conditions | Sequence editing alone does not control the host's glycan processing. |
| Study epitope accessibility | Introduce or remove a mapped surface sequon | Confirm occupancy, folding, binding and antigenicity; shielding calculations are geometric hypotheses. |
Fc sequence variants such as S298A/E333A/K334A or F243L-containing combinations can alter both receptor interaction and host-dependent glycan processing. Do not label F243L alone as a deterministic defucosylation switch. See the 2026 Fc-variant glycan study.
Experimental interpretation and verification boundary
Glycopeptide searches can support peptide identity, composition and sometimes site localization, without resolving a full glycan structure. Review localization fragments, competing assignments, search-space choices and error control. In Byonic, composition does not determine topology; O-glycosite ambiguity may remain even with an identified glycopeptide. Relative signal among detected glycoforms is not automatically absolute site occupancy; occupancy needs the appropriate modified and unmodified denominator and analytical response considerations.
Local sequence behavior is covered by synthetic tests. Public accession lookup was executed; API error handling was mocked. GlycoSHIELD source/argument handling was checked, but full conformer grafting, GROMACS SASA, DTU jobs, commercial MS software and biological performance were not executed. Supporting references record the service/source review date and unresolved access gaps.
FAQ
What does the glycoengineering skill do?
Analyzes and engineers protein glycosylation by scanning canonical N-glycosylation sequons, describing S/T-rich regions, checking curated glycan evidence, and preparing NetNGlyc, NetOGlyc and GlycoSHIELD workflows. Use for glycoprotein engineering, antibody Fc glycosylation, glycan shielding, and site-specific glycoproteomics interpretation.
How do I install glycoengineering?
Run npx skills add https://github.com/k-dense-ai/scientific-agent-skills --skill glycoengineering in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/glycoengineering/ (personal) or .claude/skills/glycoengineering/ (project).
Which AI agents can use glycoengineering?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is glycoengineering safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains glycoengineering?
It is published by k-dense-ai in k-dense-ai/scientific-agent-skills. It has 1,874 recorded installs.
More from k-dense-ai/scientific-agent-skills
scientific-writing
k-dense-ai/scientific-agent-skills
Drafts, revises, and audits scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter.
scientific-visualization
k-dense-ai/scientific-agent-skills
Creates and audits truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly. Use it for figure design, multi-panel layouts, uncertainty and missing-data displays, color/contrast review, image metadata validation, and journal export planning.
scientific-critical-thinking
k-dense-ai/scientific-agent-skills
Evaluates scientific claims and evidence quality. Applies to experimental design validity, biases and confounders, statistical interpretation, evidence grading frameworks (GRADE, Cochrane Risk of Bias), and teaching critical analysis. Supports evidence appraisal and identifying flaws; formal peer review writing belongs to peer-review.
literature-review
k-dense-ai/scientific-agent-skills
Conducts systematic, scoping, and narrative literature reviews using PubMed, arXiv, bioRxiv, Semantic Scholar, and other appropriate sources. Use for research synthesis, reproducible literature searches, screening, citation checking, or preparing Markdown and PDF reviews. Tracks search coverage, records versus studies, and evidence limitations; supports meta-analysis planning but does not supply a meta-analysis engine.
scientific-brainstorming
k-dense-ai/scientific-agent-skills
Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs. Use for early-stage research brainstorming or prioritizing candidate directions; hand off empirical validation, study design, ethics or regulatory review, and clinical questions to appropriate experts or skills.
statistical-analysis
k-dense-ai/scientific-agent-skills
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required sample sizes, or write up results - even if they never name a specific test. Covers t-tests, ANOVA, chi-square, correlation, regression, non-parametric and Bayesian methods. For low-level model APIs, see the statsmodels and pymc skills.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create 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.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available