Ibs That Symptoms

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt4_8_GLM4.7/ibs-that-symptomsThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: General SOP for common requests related to please, risk, demonstrating.

---
id: "220a96f3-adf2-4be2-8306-8b30b88f9969"
name: "ibs / that / symptoms"
description: "General SOP for common requests related to please, risk, demonstrating."
version: "0.1.19"
tags:
  - "ibs"
  - "that"
  - "symptoms"
  - "pain"
  - "chest"
  - "she"
  - "narrator"
  - "as"
  - "re"
  - "it"
  - "here"
  - "data"
  - "mining"
  - "can"
  - "what"
  - "et"
  - "latin"
  - "silvae"
  - "your"
  - "nginx"
  - "his"
  - "recording"
  - "swedien"
  - "please"
  - "risk"
  - "demonstrating"
  - "they"
  - "sap"
  - "between"
  - "quality"
  - "chart"
  - "frac"
  - "cm"
  - "times"
  - "answer"
  - "congress"
  - "their"
  - "not"
  - "chiron"
  - "text"
  - "type"
  - "name"
  - "docking"
  - "molecular"
triggers:
  - "Use when the user asks for a process or checklist."
  - "Use when you want to reuse a previously mentioned method/SOP."
examples:
  - input: "Break this into best-practice, executable steps."
---

# ibs / that / symptoms

General SOP for common requests related to please, risk, demonstrating.

## Prompt

Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>):
1) Offline OpenAI-format conversation source.
2) Title: d6ab9103f9551c7f701cf32f4e0e74b2.json#conv_1
3) Use the user questions below as the PRIMARY extraction evidence.
4) Use the full conversation below as SECONDARY context reference.
5) In the full conversation section, assistant/model replies are reference-only and not skill evidence.
6) Primary User Questions (main evidence):
7) make it short for presentation - Protein Preparation:
8) Preparing a protein for molecular docking, especially for rho kinase (ROCK), involves a meticulous series of steps aimed at ensuring its structural integrity and suitability for computational analysis. Firstly, the crystal structure of rho kinase is retrieved from a reliable protein structure database like the Protein Data Bank (PDB), ensuring high resolution and relevant ligands or co-factors if needed. Subsequently, the protein structure undergoes thorough preparation, which includes removing water molecules, heteroatoms, and any extraneous entities not pertinent to the docking study. Any structural irregularities or missing residues are corrected, and any hydrogen atoms missing from the structure are added. Energy minimization is then performed to alleviate steric clashes and optimize the protein's conformation for docking, utilizing molecular
9) modeling software such as GROMACS, CHARMM, or Schrödinger suite, along with an appropriate force field. Ligands intended for docking undergo a similar preparation process, including removal of water molecules and energy minimization to attain stable conformations. The next step involves defining a docking grid around the active site of rho kinase, crucial for guiding the docking software in predicting accurate ligand binding poses. Molecular docking is then executed using specialized software such as AutoDock, AutoDock Vina, or GOLD, docking the prepared ligands into the active site and assessing the binding affinities of resultant complexes. Following docking, thorough analysis and visualization of results are conducted to identify potential ligand-protein interactions and select promising ligand poses, facilitated by molecular visualization tools like PyMOL or VMD. Validation of docking results through experimental assays, such as enzyme inhibition assays or biochemical assays, is imperative to confirm predicted binding interactions. Further optimization may be pursued based on docking results and experimental validation, including refining ligands or conducting additional rounds of docking with modified ligands to enhance binding affinities and selectivity. Finally, meticulous documentation of all steps undertaken during protein preparation and docking is essential for reproducibility and dissemination of findings to the scientific community through publications or presentations.
10) make it short and in paragraph

For each step, include: action, checks, and failure rollback/fallback plan.
Output format: for each step number, provide status/result and what to do next.

## Triggers

- Use when the user asks for a process or checklist.
- Use when you want to reuse a previously mentioned method/SOP.

## Examples

### Example 1

Input:

  Break this into best-practice, executable steps.

Excerpt, first 4,345 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Ibs That Symptoms

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology