小满聊车小知识

什么是车身刚性关乎安全必须了解一下｜车知识 @marilyn_1003

[小满聊车小知识 @JadeOfBk]

@PhillyXoBabii 市区代步好停吗？我上次在老城区绕半天找不到能塞下一辆踏板的位置……

[小满聊车小知识 @JadeOfBk]

@razeden0 Good vibes

[B2i Digital @b2idigital]

Six of seven patients in the final dose cohort of the completed PH-762 Phase 1b trial had a response, Robert Bitterman, President and Chief Executive Officer of Phio Pharmaceuticals Corp. (@phio_pharma)(@Nasdaq :$PHIO ), told the National Investment Banking Association (@NIBAnet) 153rd Investment Conference in Fort Lauderdale, Florida, on October 7, 2026. The trial (NCT 06014086) was designed to evaluate the safety and tolerability of neoadjuvant use of intratumorally injected PH-762, an INTASYL® compound, assess the tumor response, and determine the dose or dose range for continued study.

Phio Pharmaceuticals Corp. is a B2i Digital (@b2idigital) Featured Company. See the company's in-depth profile at: https://t.co/pEllsCBPub

Bitterman also took investors through how the trial escalated its dosing, what it found on safety and what was seen at the end of the study:

• Twenty-two patients completed treatment across five dose-escalation cohorts, ending with the final cohort of seven

• No dose-limiting toxicity was found in any of the five cohorts, Bitterman said, and he described the safety and tolerability profile as very favorable

• Bitterman added that no recurrence was seen at the end of the study, which concluded earlier this year

On the depth of the responses among those six patients in the final cohort, Bitterman noted: "Four of those six were 100% cancer clear pathologically. One had a greater than 90% clearance as well."

Watch the full presentation: https://t.co/Dc770xJyYk

Phio Pharmaceuticals Corp. (Nasdaq: PHIO) is a clinical-stage biopharmaceutical company advancing its proprietary INTASYL® siRNA gene silencing technology to eliminate cancer. Phio’s INTASYL compounds are designed to enhance the body’s immune cells to more effectively kill cancer cells. Phio’s lead clinical development program is an INTASYL compound, PH-762, that silences the PD-1 gene implicated in various forms of skin cancer. The Phase 1b trial (NCT# 06014086) evaluated PH-762 for the treatment of cutaneous squamous cell carcinoma, melanoma and Merkel cell carcinoma. PH-762 is a potential non-surgical treatment for skin cancers. For additional information, visit the Company’s website, https://t.co/ENSFIYuE1Y.

Discover more Featured Companies, Featured Experts, and upcoming Featured Conferences at https://t.co/6jvWsBBx4A.

B2i Digital is not a broker-dealer or investment adviser. This post is informational and not an offer or solicitation regarding any security.

[小满聊车小知识 @JadeOfBk]

@JNewMoney 我骑的是台小排量街车，等你路线确认了我就跟着去围观，土八路就土八路吧。

[小满聊车小知识 @JadeOfBk]

@Beazy9 Gold Wing这车真属于跑长途才懂的类型，城里挪车有点累，一旦上了高速那舒适度就回不去了

[小满聊车小知识 @JadeOfBk]

@aindouglas 油箱内壁最好也看看，外面整不代表里面没锈。

[小满聊车小知识 @JadeOfBk]

@aindouglas 说像大学老师有点抬举了哈哈，我觉得更像退休的老教授，越看越有味道那种。

[xsmryze @xsmryze]

THIS IS A PURE F*CKING GOLDMINE

Anthropic just shared one of the best tricks for Claude Code.

The idea: a skill is one folder with one markdown file, and Claude only reads it when your request actually matches it.

You stop pasting the same instructions into every session, and you pay one line of context instead of the whole document.

You just make one folder:

.claude/skills/review-pr/SKILL.md

here's the split:

→ the description is the only thing sitting in context, roughly one line per skill
→ the full body loads the second a request matches that description
→ scripts in the folder get executed, never read into context
→ commit the folder and every person in the repo has the skill

three frontmatter lines do the heavy lifting:

→ allowed-tools pre-approves the tools, so it runs without a permission prompt
→ context: fork hands the skill to a subagent that never sees your chat
→ paths limits it to the files it actually belongs to

Description matches. Body loads. Scripts run.

JEV engineering is the same move one layer down: the forks that need no thinker (which skill, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split

the full tree
> .claude/skills/<name>/SKILL.md for the repo, ~/.claude/skills/ for your own
> only descriptions sit in context, the body loads on match
> keep SKILL.md under 500 lines, every line is a recurring cost once loaded
> description plus when_to_use is cut at 1,536 characters, put the trigger first
> context: fork runs it in a subagent with no conversation history
> JEV routes micro-forks in milliseconds

paste the tree and this prompt into Claude Code ↓

"Set up skills in this repo from the tree above:
1. Create .claude/skills/ and move the repeated instructions out of CLAUDE.md into one skill per job.
2. Write every description as a trigger sentence first, since the listing is cut at 1,536 characters.
3. Put anything deterministic into scripts/ and pre-approve it with allowed-tools so it runs without a prompt.
4. Route fast deterministic forks (which skill, which tool, retries) through JEV.
Show me every change as a diff first. No edits until I say go."

↳ https://t.co/nmxR8sUXOc

save it, it'll come in handy.

[小满聊车小知识 @JadeOfBk]

@nomerce 很多人拿这台跟同价位复古车比配置，我倒更喜欢它不急着堆参数的选择。

[biektropic @biektive]

YOUR GROK BOT IS CHARGING YOU 24/7 FOR A JOB THAT TAKES 5 MINUTES.

One routine.
8,640 wake-ups a month.
Most of them find absolutely nothing.

> Every 5 minutes: $400/month
> Every hour: $33/month
> Same job: 12× cost difference

That's how always-on AI quietly eats your allowance.

The bot still wakes up, reads the context and burns money.

Use a webhook when possible.

Use a cheap change-check before the full model.

Slow the schedule down until a real miss proves you need speed.

One routine can save roughly $367/month under the Article’s assumptions.

Ten routines can keep about $3,670 in your pocket.

Before hiring another AI employee, stop paying the ones doing f*ck all.